October 3, 2019 at 7:14 pm
I have a customer who has assemblies that are being used in SQL Server 2012. We're in the process of migrating 4 databases into one. The only way that I can get the assemblies to into the new SQL Server 2017 instance is by using bad security practices by disabling clr strict security and using TRUSTWORTHY ON.
I have access to the DLL files, however, not to the source code. Is there a way to create an Asymmetric Key and login with just having the DLL files?
October 4, 2019 at 9:16 am
I've always found with migrating CLR assemblies that you are better off scripting it from your old server
it will generate a CREATE assembly script that includes a big old binary string. just apply that to your new server, you won't need the DLL file
MVDBA
October 4, 2019 at 12:36 pm
dotPeek could decompile the dll's if you'd like to see the source code. It's free and there's no registration or email required to download and install it.
https://www.jetbrains.com/decompiler/download/
Aus dem Paradies, das Cantor uns geschaffen, soll uns niemand vertreiben können
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply