Erica Thompson 0660ea6fac
Update README (#31244)
* Update README

Let contributors know that docs will now be located in UDR

* Add comments to each mdx doc

Comment has been added to all mdx docs that are not partials

* chore: added changelog

changelog check failure

* wip: removed changelog

* Fix content errors

* Doc spacing

* Update website/content/docs/deploy/kubernetes/vso/helm.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

---------

Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2025-07-22 08:12:22 -07:00

46 lines
1.9 KiB
Plaintext

---
layout: docs
page_title: Upgrade the Vault EKM provider
description: Upgrade steps for the Vault EKM provider for Microsoft SQL Server.
---
> [!IMPORTANT]
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
# Upgrade the Vault EKM provider
~> **Note:** The upgrade process will put the database into maintenance mode and
require a restart. It is highly recommended to test this procedure in a
staging environment prior to running it on a production database.
1. Disable the Vault EKM Provider, and verify it is marked disabled:
```sql
ALTER CRYPTOGRAPHIC PROVIDER TransitVaultProvider DISABLE;
SELECT * FROM sys.cryptographic_providers;
```
1. Install the latest version from [releases.hashicorp.com][releases], following
the instructions in the installer.
1. If you get a "Files in Use" prompt while running the installer, select
"Do not close applications. A reboot will be required", and restart
after the installation has completed.
1. Reload the provider DLL:
```sql
ALTER CRYPTOGRAPHIC PROVIDER TransitVaultProvider
FROM FILE = 'C:\Program Files\HashiCorp\Transit Vault EKM Provider\TransitVaultEKM.dll';
```
1. Now re-enable the Vault EKM Provider and verify it is both marked enabled
and the version reported matches the version of the installer:
```sql
ALTER CRYPTOGRAPHIC PROVIDER TransitVaultProvider ENABLE;
SELECT * FROM sys.cryptographic_providers;
```
1. Finally, restart Microsoft SQL Server.
[releases]: https://releases.hashicorp.com/vault-mssql-ekm-provider/