Migrating a SQL Database with CLR Integration from Old SQL Server Versions

Bruno van Dooren

Rate me:

5.00/5 (2 votes)

4 May 2023CPOL6 min read

7.3K

Ways to deal with changed security for CLR code in SQL databases

When moving a CLR integrated database from an old SQL version (say 2008R2) to something more modern (say 2016 or higher), the security configuration changes. The old way of configuring security for imported assemblies no longer works. In this article, I explore some options for dealing with that for the purpose of doing a successful migration.

Views

Daily Counts

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

Bruno van Dooren

Software Developer

Belgium

I am a former professional software developer (now a system admin) with an interest in everything that is about making hardware work. In the course of my work, I have programmed device drivers and services on Windows and linux.

I have written firmware for embedded devices in C and assembly language, and have designed and implemented real-time applications for testing of satellite payload equipment.

Generally, finding out how to interface hardware with software is my hobby and job.

Migrating a SQL Database with CLR Integration from Old SQL Server Versions

Views

License

Comments and Discussions