Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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
share|improve this question

1 Answer 1

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.

share|improve this answer
    
@squilman: Not exactly an answer to my question but worth knowing those implications on using SqlCLR; Thanks. –  Sung Jan 21 '10 at 20:53
    
@Sung Meister: what type of info are you looking for then? –  squillman Jan 21 '10 at 21:26
    
@squilman: sorry about the delay on response. I have decided not to go with SQL CLR for the particular problem I was having - I created a windows services instead. –  Sung Jan 29 '10 at 5:13

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.