Exceptional Condition Handling in SQL Server 2005
This is my second part of the SQL Server 2005 posts; you can read the first part on Hosting the .NET runtime in SQL Server. In the CLR certain conditions such as out of memory, stack overflow, etc can bring down an app domain (or process), this cannot be allowed in SQL Server 2005 when latter is acting has a host (for the CLR) as it will affect reliability and performance - couple of the key goals for SQL Server. Similarly unconditionally stopping a thread (e.g. via Thread.Abort) can potentially leave some resources in a “hung” state. ...