| |
 |
|
SQL Server Tips by Burleson |
SQL Server 2005 and extended
stored procedures
With the integration of the .NET framework 2.0 in SQL Server 2005,
stored procedures and user-defined functions can be created in
VB.NET or C#. This is a powerful new addition from a developer’s
perspective and it will be very useful. However, there is a time and
a place for using each technology properly. A stored procedure that
uses mostly set based operations should be coded in TSQL. If it
calls a user-defined function with some slow calculations, then the
function should be in .NET code or an XP (for maximum performance,
to access external libraries, use functionality that the .NET
framework Base Class Libraries are missing, etc).
SQL Server 2005 can use the same XP's as SQL Server 2000, which is
great because the code developed today will also run when upgrading
in the future. In fact all of the major XP’s we present in the book
have been tested on SQL Server 2005 in addition to SQL Server 2000.
The latest version available to the authors at the time of writing
was the December 2004 Community Technology Preview and that is what
was used for the testing. The only unusual issues discovered was
with XP_IPCONFIG, which is described in Chapter 20. The issue seems
to be a bug in the new client programs, which are provided as a
replacement for the venerable Query Analyzer. These new utilities,
namely “SQL Server Management Studio” and “SQL Server Express
Manager” report spurious errors when an XP is run which returns
multiple recordsets. If Query Analyzer is used to run the exact same
query against SQL Server 2005, no problems occur. Hopefully these
kinds of issues will be ironed out before the final release of SQL
Server 2005.
The above book excerpt is from:
Super SQL
Server Systems
Turbocharge Database Performance with C++ External Procedures
ISBN:
0-9761573-2-2
Joseph Gama, P. J. Naughter
http://www.rampant-books.com/book_2005_2_sql_server_external_procedures.htm |
