I've met quite a few developers over the years that loathe T-SQL. Personally, I've been a huge fan of T-SQL (within SQL Server specifically) for many years and became even more so during my contract with APS. This was largely due to the fact that there were a couple of very talented SQL Server gurus working there that were quite willing to share "tips and tricks" and point out good vs.. bad database development techniques. Today, I was reading through an an MSDN article Using CLR Integration in SQL Server 2005 while eating lunch and found the following:
Even before CLR support was introduced in SQL Server, it has always been important to recognize that database applications should use the query language as much as possible. Database applications should take advantage of the set-oriented query processor and only resort to procedural programming for expressing logic that cannot be expressed within the query language. This remains true with CLR support in SQL Server. CLR should not be used to write procedural code that can be expressed in a single SELECT statement...Developers attempting to use CLR features should ensure that they are taking full advantage of the query language, including the extensions in SQL Server 2005. They should look at CLR as an efficient alternative for logic that cannot be expressed declaratively in the query language.
The developers that truly hate T-SQL, end up doing the exact opposite of this recommendation - writing what should be T-SQL logic in the application code. My opinion is that in order to be a great developer on database applications, you should embrace T-SQL, not fear and avoid it. However, that's not really the main point of the article. Take a look and enjoy the new features of SQL Server 2005 and its ability to interact with the .NET CLR.
