advertisement
Login | Register   
  Include Code  Search Tips
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   TIP BANK
Browse DevX
Download the code for this article
Partners & Affiliates
advertisement
advertisement
advertisement
advertisement
 

Choosing Between the CLR and T-SQL in SQL Server 2005

The CLR integration features in SQL Server 2005 enable managed code to run inside the database, but developers now need to choose between CLR-based features and T-SQL when building applications. Find out when each is appropriate. 


advertisement
icrosoft's integration of the .NET Framework and the CLR directly into the database engine in SQL Server 2005 is a key enhancement. The result is a major paradigm shift for database application developers and administrators, who can leverage the new functionality in many different ways. In this article, you'll gain insight into this new programmability architecture, and get some tips on how to choose between the new features and the familiar T-SQL language when building your applications.


Why Use SQLCLR?
SQLCLR is Microsoft's name for the integration of the CLR as a hosted runtime within SQL Server, enabling the execution of managed code inside the database. SQL Server 2005 is highly integrated with the .NET Framework, letting you create stored procedures, functions, user-defined types, and user-defined aggregates using your favorite .NET programming language. All these constructs can take advantage of large portions of the .NET Framework infrastructure, the base class library, and third-party managed libraries.

It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com.
Already a member?



advertisement