![]() ![]() However, this is not recommended because results are not reliable when a corrupted state exception occurs.ĭue to the strict security requirements of SQL Server 2012 (11.x), CLR database components will continue to use the Code Access Security model defined in CLR version 2.0. These exceptions can still be caught by the CLR database components by setting a code attribute ( Element). These exceptions are now caught in the CLR integration hosting layer. In version 4 of the CLR, CLR database objects no longer catch corrupted state exceptions. ![]() The following are new features in CLR integration in SQL Server 2012 (11.x): Applies to: SQL Server (all supported versions)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |