All of a sudden I'm getting errors when I try to deploy (using TSQL) a method in an assembly.
I have a TSQL script that worked a few days ago, it creates a few assemblies (i.e. it installs them from file images) using CREATE ASSEMBLY and then it creates a stored proc in one of the assemblies using CREATE PROCEDURE.
I am now getting
Assembly 'ClrEvaluation.Utilities' is not visible for creating SQL objects. Use ALTER ASSEMBLY to change the assembly visibility.
I never saw this over the past few weeks of testing, the script I uses to install and uninstall was working fine and hasn't changed.
It is possible that the dependency relationships between the assemblies has changed (because we have modified our code recently) but this error message doesn't even hint at this as a possible explanation, but I am going to check into this.
Finally I am amazed that a product as sophisticated as SQL Server 2008 R2 has these shortcomings:
1) The tree view in SQLSMS must be manually right-clicked and "refreshed" all the time, else it gets out of date. This is frankly inexcusable and I am forever scrolling up and down the tree view to find a parent node and force it to refresh (Ive coded with
TreeView a lot and I can't see why MS have allowed this out the doo
View Complete Post