INTRODUCTION srv_describe(pSrvProc, 1, Column 1 , SRV_NULLTERM, SRVVARCHAR, strlen(szText),

INTRODUCTION srv_describe(pSrvProc, 1, Column 1 , SRV_NULLTERM, SRVVARCHAR, strlen(szText), SRVVARCHAR, 0, NULL); // set column length and data srv_setcollen(pSrvProc, 1, strlen(szText)); srv_setcoldata(pSrvProc, 1, szText); // send row srv_sendrow(pSrvProc); // send done message srv_senddone(pSrvProc, (SRV_DONE_COUNT | SRV_DONE_MORE), 0, 1); return (XP_NOERROR); } SQL Server uses structured exception handling to wrap all calls to extended stored procedures. This prevents unhandled exceptions from damaging or shutting down SQL Server. There is, however, no way for SQL Server to prevent an extended stored procedure from misusing system resources. A rogue extended stored procedure could call the exit() function in the Windows runtime library and shut down SQL Server. Likewise, SQL Server cannot prevent a poorly coded extended stored procedure from writing over the memory SQL Server is using. This direct access to system resources is the reason that extended stored procedures are more efficient than T-SQL for non data access operations, but is also the reason that a stored procedure must undergo much more scrutiny before it is added to SQL Server. Under SQL Server 2005, T-SQL code continues to operate mostly as before. In addition to providing complete compatibility with existing code, this enables the millions of current T-SQL programmers to continue to write high-performance data access code for the SQL Server relational engine. For these programmers, T-SQL is still their language of choice. SQL Server 2005 adds the ability to write stored procedures, user- defined functions, and triggers in any .NET-compatible language. This enables .NET programmers to use their language of choice, such as C# or VB.NET, to write SQL Server procedural code. The .NET code that SQL Server runs is completely isolated from SQL Server itself. SQL Server uses a construct in .NET called an AppDomain. It completely isolates all resources that the .NET code uses from the resources that SQL Server uses, even though both SQL Server and the

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Tomcat Web Hosting services

Bookmark the permalink.

Comments are closed.