I am trying to deploy a CLR function (which computes a hash of a text or a file, not available from SQL Server) for the first time on a production server.
I was able to test the function on a development machine but I am still wondering,
Are there any list of gotchas to consider before turning on the CLR option?
sp_configure 'clr enabled', 1;
GO
RECONFIGURE;
GO
I think you'll find all (or at least a goodly amount) of the info you want at this MSDN article directly related to the subject:
CLR Integration Security
Although I doubt that it directly relates to your situation, I have seen one big gotcha when calling unmanaged code from an an assembly. Something along the lines of this post.
Also, any dependencies that your assembly requires also have to be registered with SQL. Even things like System.dll. That can get ugly. Very few assemblies are blessed by SQL by default.