May 16, 2011 at 7:59 am
I know that EXTERNAL_ACCESS and UNSAFE assemblies cannot be created in a SQL Server database, unless they are either signed or the TRUSTWORTHY bit is set to ON.
SAFE assemblies, on the other hand, can be created as signed or unsigned.
What would be the advantages of signing a SAFE assembly?
I know one of them is that no third party would be able to alter its contents.
Are there any other reasons why signing a SAFE assembly would be worth it?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
May 16, 2011 at 9:10 am
I think that's it. It's a verification of the creator/author of the assembly.
May 16, 2011 at 9:19 am
OK, thank you!
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply