Menu
This is the situation:
I have a Trigger.dll and a Trigger.XmlSerializer.dll.
I use CREATE ASSEMBLY to register them in MSSQL.
Now, I have compiled new versions of both.
I want to use ALTER ASSEMBLY to update them, however you can only update one at a time. If you try to update one that has a dependency, it complains. What's the trick to doing this?
I don't want to drop and recreate as I have to then drop all the triggers, etc. and there is database downtime.
394
Deployed User CLR assemblies are stored in the database you deploy them to, not on the file system. the column called content contains binary data is the assembly.
To determine if CLR is enabled, execute the following commands: EXEC SP_CONFIGURE 'show advanced options', '1'; RECONFIGURE WITH OVERRIDE; EXEC SP_CONFIGURE 'clr enabled';
NET Framework common language runtime (CLR), instead of in Transact-SQL. An assembly in SQL Server is an object that references a managed application module (. dll file) that was created in the . NET Framework common language runtime. An assembly contains class metadata and managed code.
according to the microsoft support you can use it by trick.
Notes
To upgrade or downgrade assembly A, follow these steps.
108
I fear dropping the table and re-creating it is the only way.
The main reason for this is that values stored in a type in an assembly, are unusable if you update the assembly to a new version.
37
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
