SQL Server Performance

Performace overhead and resolution when using CLR vs TSQL

Discussion in 'Other SQL Server Blogs around the Web' started by Anonymous, Jul 31, 2007.

  1. Anonymous New Member

    Integration with .NET framework CLR within SQL Server gives extra flexibility for the developers to use other programming languages such as C# or VB.net by creating functions, stored procedures, triggers, data types, and aggregates are among the kinds of business logic that programmers can write with these languages. But think about performance overhead in using such features on a large scale basis. IMHO if the same business logic can be implemented using Transact SQL (TSQL) then it is best to go...(<a href="http://sqlserver-qa.net/blogs/t-sql/archive/2007/07/31/1192.aspx">read more</a>)<img src="http://sqlserver-qa.net/aggbug.aspx?PostID=1192" width="1" height="1">

Share This Page