July 17, 2024 at 12:00 am
Comments posted to this topic are about the item Updating a Cryptographic Provider for EKM with Azure Key Vault - Level 5 of the Stairway to TDE
Vishnu Gupthan
PowershellAcademy
www.powershellacademy.com
July 17, 2024 at 3:17 pm
Upgrading a cryptographic provider can be accomplished without restarting the instance or dropping the provider, with the key provision that this only works if the name of the provider file does not change.
You can rename the provider .dll file in Windows even if it is use. Once SQL Server open the file, it uses a pointer to the file for further operations - not the file name. This allows replacing the EKM dll without a restart:
I've used this technique many times on busy multi-TB databases. It's safe and silent.
Note that if you are updating the provider file because the Authenticode signature is expiring, you still won't need to restart, even if the signature expired while the server was running. The signature is checked only when the provider is loaded (usually at startup).
Eddie Wuerch
MCM: SQL
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply