Вот что ответил один из разработчиков по поводу CLR
There were bunch of issues we had to solve. Some of them include:
— Sharing process's resources between SQL Server and CLR
— Diferent execution models of SQL Server and CLR
— CLR didn't have notion of nonpreemptive scheduling
— Mismatch in exception models
— CLR hasn't been design to be a database component:
— Stability of CLR
— Prone to unresolvable deadlocks
— Fail fast
And much more
Grigory
данное сообщение получено с www.gotdotnet.ru
ссылка на оригинальное сообщение
