Hi,
I install sql compare and run into one situation that can't done without manually job.
I have the assembly that have to have 'TRUSTWORTHY' database property.
It realy would be nice that I can compare database property, and that I can via SQL compare change that property to deploy assembly.
radovan
The following error message was returned from the SQL Server:
[10327] CREATE ASSEMBLY for assembly 'AI.WMS.SQL.Helpers' failed because assembly 'AI.WMS.SQL.Helpers' is not authorized for PERMISSION_SET = UNSAFE. The assembly is authorized when either of the following is true: the database owner (DBO) has UNSAFE ASSEMBLY permission and the database has the TRUSTWORTHY database property on; or the assembly is signed with a certificate or an asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. If you have restored or attached this database, make sure the database owner is mapped to the correct login on this server. If not, use sp_changedbowner to fix the problem.
The following SQL command caused the error:
I install sql compare and run into one situation that can't done without manually job.
I have the assembly that have to have 'TRUSTWORTHY' database property.
It realy would be nice that I can compare database property, and that I can via SQL compare change that property to deploy assembly.
radovan
The following error message was returned from the SQL Server:
[10327] CREATE ASSEMBLY for assembly 'AI.WMS.SQL.Helpers' failed because assembly 'AI.WMS.SQL.Helpers' is not authorized for PERMISSION_SET = UNSAFE. The assembly is authorized when either of the following is true: the database owner (DBO) has UNSAFE ASSEMBLY permission and the database has the TRUSTWORTHY database property on; or the assembly is signed with a certificate or an asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. If you have restored or attached this database, make sure the database owner is mapped to the correct login on this server. If not, use sp_changedbowner to fix the problem.
The following SQL command caused the error: