4

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
HopelessN00b
  • 53,385
  • 32
  • 133
  • 208
dance2die
  • 1,961
  • 7
  • 31
  • 40

1 Answers1

3

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.

squillman
  • 37,618
  • 10
  • 90
  • 145
  • @squilman: Not exactly an answer to my question but worth knowing those implications on using SqlCLR; Thanks. – dance2die 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. – dance2die Jan 29 '10 at 05:13
  • Old post I know but just came across it - there are a number of assemblies already available - including System.dll - the full list for SQL Server 2005 can be found at https://msdn.microsoft.com/en-us/library/ms403279%28v=sql.90%29.aspx (page also has a link to other SQL Server versions which have added more assemblies - e.g. 2014 also supports System.Xml.Linq.dll) – mecsco Jul 01 '15 at 11:01