MY biggest concern is for a potential Database engine performance hit, and will current SQL Server optimum memory requirements be increased - if so, how much?  Also, will SQL Server 2005 install on systems that don't already have the .NET framework installed?

J. Chris Gibson

My opinion is that it will be beneficial to have a "procedural language" available to perform functions that TSQL is not as adept at.  That is available today on the client side, obviously, but not quite so close to the data itself.  This will most likely create opportunities to make faster data access available to the other application tiers.

Now, I'm not ready to go all chicken little and claim that C# will ruin my database, because it is not the best tool for getting data in and out of a database *in the general case*.  I don't believe that the presentation tier guys are going to ask for CLR in the database because they are used to having the recordsets handed to them ready-to-go.  What I do see is that I can find a better (faster) way to get them data in very specialized cases and for that I shall be eternally grateful.

We'll see what happens...

jg

I entirely agree.  In fact, I've just returned from a T-SQL course with Learning Tree and so am very pro T-SQL at the moment.  I think in the interim it'll be a case of finding my (and everybody else's) feet to discover which procedures are going to perform better depending on what language they're written in.