>> By providing multi-language support in a critical business component, Microsoft are opening Pandora's box in many ways; i.e. the DBA's with their finely tuned indices, rules and constraints are suddenly going to find a multitude of new data handling sub-processes affecting their systems.

This is one of my biggest fears. I'll get a call to go to a client that is having performance problems and find a bunch of stored procedures written in COBOL ;-)

Actually the one flaw in this thought is the assumption that the SQL Server would be open other besides the DBAs. This is very rare. Most customers lock down their SQL Server such that only DBAs have access.

-Mike


>Whilst I don't dispute your assertion, I'm not wholly convinced that providing the CLR in Yukon is actually going to bring improvements to data processing systems. By providing multi-language support in a critical business component, Microsoft are opening Pandora's box in many ways; i.e. the DBA's with their finely tuned indices, rules and constraints are suddenly going to find a multitude of new data handling sub-processes affecting their systems.
>
>I hope that Microsoft have thought of this in their other alterations to Yukon, i.e. providing a better indexing wizard than their current offering; as data access patterns will alter considerably when any .Net programmer can claim to be a SQL Server programmer by default.
>
>Just a thought,
>Simon