Interesting and more than anything else the fear for the mamoth list of new features will surely weigh on all the DBA's. You need to understand that even though there is tons of features to lookout for as a developer the DBA's are NOT left behind. The server
is now open and has lots of interesting system tables i.e. in SQL Server 2005 we call them as DMV;s and DMF's that have redefined the way administration would be done. From a better availability and secure code perspective it must be noted that introduction
of SQLCLR reduces the need to host and run buggy extended stored procedures. Hence it is better ... If there is a need to use SQLCLR in the unsafe mode then the person deploying must have sysadmin previledges. hence I would say, dont deploy using a sysadmin
previledge, doing this you will be able to find what the code will be doing behind the scenes and how safe it is. Using the safe operation is highly recommended and most of the activity can be achieved with this functionality.
Potty: Given the timespan I just gave an overview of the features. For a matter of fact we can take detailed sessions on each topic for hours though.
Abhishek: Comminities are close to my heart too and for the very reason had to highlight some of the activities that we do in Bangalore, India. I think we will get more people interested in doing cummunity activities.
Tekmaven: Your concern and *assumption* is like what most of the people think. I recently wrote an article "Making the most of CLR" for SQL Server Magazine on this very topic. If you have a subscription then read it:
http://www.windowsitpro.com/Article/ArticleID/45673/45673.html. It is NOT always that CLR will be slower than T-SQL. Yes, for data intensive tasks the bet would surely go for T-SQL
as it is closer to data. But on the contrary think of all the other activities that T-SQL is not elegant or should I say optimized for like heavy string manipulations, math calculations. Here I see CLR can surely outperform. Typical example would be to use
RegEx type of funtionality that sometimes would be impossible to implement. Next as discussed in the video trying to write Extended Stored procedures or calling a webservice, implementing system operations as Eventlog or File IO operations. I feel here CLR
does get an edge. So we need to weigh our options before implementing them. Just my $.20 ...