Is it a good-practice to enable SQL Server CLR integration in a server-cluster scenario? The policy at my organization disallows deploying CLR assemblies on their production servers; I was informed by the DBA's this is because the CLR UDFs runs in-process and the databases are on a cluster.
I'm just curious if the policy is to simplify the DB admin (and perhaps ensure all code is open for review by DBA's), or is there a technical reason to prohibit CLR integration in a server-cluster scenario? Thread safety?
- Threading in CLR in SQL Server 2008
- IN SQL Server is CLR Threadsafe
- Why doesn't SQL Server come preinstalled with .net Framework for CLR Integration?
(By the way, my primary use-case is for string-manipulation UDFs, as described in this answer)