Friday, November 9, 2007 11:06 AM
xmldeveloper
CLR disabled in SQL Server 2008
What do you think will happen after running the next code:
EXEC sp_configure 'clr_enabled',0
RECONFIGURE
GO
Answer: Disabling SQLCLR.
Really?
Not quite. If you read Books Online it says:
"Use the clr enabled option to specify whether user assemblies can be run by Microsoft SQL Server." and also "Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling. Features that rely upon CLR and that do not work properly in fiber mode include the hierarchy data type, replication, and Declarative Management Framework."
So SQLCLR cannot be disabled because system data types (such as HierarchyID, Geometry, Geography), Declarative Management Framework and Change Data Capture need CLR.
Why?
For start - HierarchyID, Geometry and Geography data types are implemented as CLR User-Defined types.
Then, if you watch the replay for the June CTP webcast about Declarative Management Framework you would have a chance to see its architecture and why it needs CLR:
To conclude, you can enable/disable CLR user-written code but not SQLCLR itself.
Bob Beauchemin has a series of posts on this topic if you want to read more: