It appears that CLR integration does not like Dotnet framework 2.0 sp2. I am getting the following error message when trying to run code that depends on the clr. Msg 6510, Level 16, State 11, Line 1 Common Language Runtime (CLR) v2.0.50727 not installed properly. The CLR is required to use SQL/CLR features. I have verfied with the dotnet verification tool that the dotnet framework for all versions installed work. I have only found possibly [...]

We inherited a legacy SQL 2005 database. Two assemblies were setup to be used by triggers in one of the databases (ouch). The folder/files were delted by mistake. They were installed by a previous employee from his desktop folder, and did not get checked into source control (double ouch). Now that the dll’s are gone, we are concerned about a reboot. Does SQL 2005 copy/rename/store those dll’s in such a way that would mean a [...]

How can i update a CLR function (or procedure) assembly dll without having to drop and re-create the assembly in SQL Server (2008 R2)? As it stands now if i update an assembly (e.g. to add a new function), SQL Server will not honor the updated dll until i drop the assembly: DROP ASSEMBLY CLRFunctionsMsg 6590, Level 16, State 1, Line 1 DROP ASSEMBLY failed because ‘CLRFunctions’ is referenced by object ‘NormalizeString’. But before i [...]

One of our in-house applications has a SQLCLR assembly which is currently experiencing problems. The developer is having problems recreating the issue using the version that is stored in our source control system, so he suspects that some code may have been released that was not uploaded to source control. Is there a way to extract a SQLCLR assembly into a .dll file so that he can reverse engineer it for analysis? There is indeed [...]