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.
Hmmm ... I had lots to talk and very less time. Hence would have been a bit fast . Will take care next time round. Thanks for your feedbacks. I will work on the other request and try to give you some more examples. Catch the SQLCLR Team blog at:http://blogs.msdn.com/sqlclr/. This has some fabulous implementations and interpretations of using CLR inside SQL. Couple other resources include: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sqlclrguidance.asp and http://msdn.microsoft.com/library/en-us/dnsql90/html/xmlshowplans.asp.
Hope this helped.