That said, many people have run performance tests and the general consensus is that T-SQL will always perform better for standard CRUD (Create, Read, Update, Delete) operations, whereas CLR code will perform better for complex math, string manipulation and other tasks that go beyond data access.
SQL Server MVP Gustavo Larriera has compiled the following list of useful links with more information on this topic:
- Using CLR Integration in SQL Server 2005
- An Intro to CLR Integration in SQL Server 2005
- Choosing Between the CLR and T-SQL in SQL Server 2005
- Introducing SQL Server 2005's CLR Integration
- SQL Server Chat: SQL Server 2005 Beta 2 CLR Q&A
- DBAs Bar Door Against Big Bad .NET Wolf
- User Defined Function performance comparison
Do you have comments on this Ask the Expert Q&A? Let us know.
Dig Deeper on Microsoft SQL Server 2005
Related Q&A from Adam Machanic
Migrating to SQL Server 2005 from SQL Server 2000 is a hefty feat when compared to upgrading from 7.0 to SQL Server 2000. Site expert Adam Machanic ... Continue Reading
Multiple readers can sometimes read the same row simultaneously causing a false result. SQL Server 2005 expert Adam Machanic suggests modifying the ... Continue Reading
SQL Server 2005 and T-SQL do have differences. The advantages and disadvantages would depend user environment as described by SQL Server 2005 expert... Continue Reading