Certificate management (SQL Server Configuration Manager)
Applies to: SQL Server - Windows only
This article describes how to deploy and manage certificates across your SQL Server Always On failover cluster instance (FCI) or availability group (AG) topology.
SSL/TLS certificates are widely used to secure access to SQL Server. With earlier versions of SQL Server, organizations with large SQL Server estates had to spend considerable effort to maintain their SQL Server certificate infrastructure, often through developing scripts and running manual commands.
With SQL Server 2019 (15.x) and later versions, certificate management is integrated into the SQL Server Configuration Manager, which simplifies the following common tasks:
- View and validate certificates installed in a SQL Server instance.
- Identify which certificates might be close to expiring.
- Deploy certificates across AG machines from the node hosting the primary replica.
- Deploy certificates across FCI machines from the active node.
You can use certificate management in SQL Server Configuration Manager with earlier versions of SQL Server, starting with SQL Server 2008 (10.0.x).
Note
These instructions apply to SQL Server Configuration Manager for SQL Server 2019 (15.x) and later versions. For SQL Server 2017 (14.x) and earlier versions, see Certificate management (SQL Server 2017 Configuration Manager).
Note
These instructions apply to SQL Server Configuration Manager for SQL Server 2017 (14.x) and earlier versions. For SQL Server 2019 (15.x) and later versions, see Certificate management (SQL Server 2019 Configuration Manager).
In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.
Right-click Protocols for <instance Name>, and then select Properties.
Choose the Certificate tab, and then select Import.
Select Browse and then select the certificate file.
Select Next to validate the certificate. If there are no errors, select Next to import the certificate to the local instance.
In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.
Right-click Protocols for <instance Name>, and then select Properties.
Select a certificate from the Certificate dropdown list, and then select Apply.
Select OK.
For a failover cluster instance (FCI) configuration, complete these steps in the active node of the FCI. You must have administrator permissions on all the cluster nodes.
For an availability group (AG) configuration, complete these steps from the node hosting the AG primary replica. You must have administrator permissions on all the cluster nodes.
In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.
Right-click Protocols for <instance Name>, and then choose Properties.
Choose the Certificate tab, and then select Import.
Select the certificate type, and whether to import for the current node only, or for each individual cluster node.
If installing for a single node, choose Browse and select certificate file. Then skip to step 8.
If installing a certificate for each node, select Next to list possible owner nodes. Possible owners for the current FCI are preselected.
Choose Next to select the certificate to be imported.
Enter the password when prompted. Look for any warnings or errors after validation.
Select Next to import the selected certificates.
Note
Complete these steps in the active node of the FCI. User must have administrator permissions on all the cluster nodes.
In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.
Right-click Protocols for <instance Name>, and then select Properties.
Choose the Certificate tab, and then select Import.
Choose the certificate type and select Next to select from the list of known availability groups.
Select Next to choose certificates for each replica node. Certificates should have a file name that matches the netbios name of the nodes.
Select Next to import the certificate on each node.
Note
Complete these steps from the node hosting the AG primary replica. User must have administrator permissions on all the cluster nodes.