You have imported an assembly into a SQL Server database to use the CLR functions and stored procedures it contains. However later, you lost the original .dll file and you would like to create the .dll file again from what's in the database. In this tip, we look at how you can recreate the .dll file.
SQL Server 2012 supports SHA-256 and SHA-512 through the HASHBYTES() function, but earlier versions of SQL Server do not. SHA-256, SHA-384 and SHA-512 can, however, be implemented in SQL Server 2005 or SQL Server 2008 with the CLR assembly described in this article.
Sometimes a procedure returns more than 1 result set. The article describes how to save all result sets into new database tables
Three CLR-resident functions for 16-, 32-, and 64-bit FNV1a hashing
Are Common Language Runtime routines in SQL Server faster or slower than the equivalent T-SQL code? How would you go about testing the relative performance objectively? Solomon Rutzky creates a test framework to try to answer the question and comes up with some surprising results that you can check for yourself.
How to create external_access CLR assembly on remote MS SQL server, when trustworthy option is forbidden, and only SQL login is available
I run this code on SQL Server 2019:
DBCC CLONEDATABASE(imdb, imdb_dev)I then change to the cloned database, imdb_dev, and run some queries. I then run this code while testing:
INSERT dbo.Title (TitleID, Title, DateReleased) VALUES (3234, 'Maestro', '2023') GOWhat happens? See possible answers