Hi. One of my databases has an assembly that uses system.web. Therefore, in the deploy script, the developer has put in a create assembly for it like so Create Assembly [System.Web] FROM 'C:WINDOWSMicrosoft.NETFrameworkv2.0.50727System.Web.dll' WITH PERMISSION_SET = UNSAFE followed by the create assembly statements for the actual bespoke assemblies. The deploy script all works fine, as do the assemblies it creates. However, when SQL restarts, the calls to the assemblies no longer work, and the only way to get them to is to run the deploy script (which drops them if they exist and recreates them) again. Not particularly familiar with 2005 & CLR. Is this normal behaviour (I would have expected that once deployed, they were there after re-boot). If it's not how things are supposed to work, what's wrong, and how do I fix it? Thanks
