消息：6528，在数据库“XYZ”的 SQL 目录中找不到程序集“XYZCLRDatabase”

Question

I executed the following command to my database and it give me the message Commands completed successfully.

USE XYZ
GO
DECLARE @clrName nvarchar(4000) = 'XYZCLRDatabase, ...';
DECLARE @asmBin varbinary(max) = <bindary>;
DECLARE @hash varbinary(64);

SELECT @hash = HASHBYTES('SHA2_512', @asmBin);

EXEC sys.sp_add_trusted_assembly @hash = @hash,
                                @description = @clrName;
GO

It also shows the same record into the sys.trusted_assemblies table.

But it does not listed into the Assemblies folder...

XYZ database > Programmability > Assemblies

When I am trying to create the Stored Procedures with the following code I get the error.

USE XYZ
GO
CREATE PROCEDURE SPName @sqlXml XML, @flag1 bit, @flag2 bit, @id int null, @flag3 bit
AS
EXTERNAL NAME XYZCLRDatabase.StoredProcedures.MYClrSP

I get the following error message:

Msg 6528, Level 16, State 1, Procedure SPName, Line 1 [Batch Start Line 23]
Assembly 'XYZCLRDatabase' could not be found in the SQL catalog for database 'XYZ'.

what goes wrong....

Answer 1

While bradbury9 is correct that the CREATE ASSEMBLY statement is missing, PLEASE DO NOT enable TRUSTWORTHY in your database,!! Not only is it an unnecessary security risk, it's also absolutely useless when either using "trusted assemblies" or the much preferred signing the assemblies. Both of those cases ("trusted assemblies" and signing the assemblies) exist so that you don't need to set the database to TRUSTWORTHY ON (meaning: either set TRUSTWORTHY ON XOR sign the assemblies / add them as "trusted assemblies"; doing either one of the latter options means that you do not set TRUSTWORTHY ON ). For more info on why you shouldn't enable TRUSTWORTHY and the preferred alternative (ie Module Signing ), please see:

PLEASE, Please, please Stop Using Impersonation, TRUSTWORTHY, and Cross-DB Ownership Chaining

Additionally, "trusted assemblies", while not nearly as bad as TRUSTWORTHY ON , isn't ideal either as there are several problems with that feature . Signing the assemblies, either outside of SQL Server (preferred) or even inside SQL Server, is far better. Please see my answer to the following question, also here on SO, for your best options (see the bottom half, below the line):

CLR Strict Security on SQL Server 2017

Answer 2

You are missing the CREATE ASSEMBLY instruction. In summary, the steps to add an assembly in SQL Server are:

1. Make sure the SQL Server instance allows CLR: EXEC sp_configure 'clr enabled', 1; RECONFIGURE; EXEC sp_configure 'clr enabled', 1; RECONFIGURE;

   This step (#1) should only be required once.

2. Call the sp_add_trusted_assembly stored procedure

3. Call the CREATE ASSEMBLY instruction