Problem: I read in a PCI security tip that I should configure Secure Sockets Layer (SSL) encryption on our SQL Servers, but this requires a trusted certificate. Could you please help me with how to complete this task?

SSL/TLS certificates can be used by SQL Server in order to encrypt all communication between a SQL Server instance and its client connections, by encrypting the communication channel. It’s useful for PCI security and SQL Server Audit also.

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, certificate management is integrated into the SQL Server Configuration Manager, simplifying common tasks such as:

  • Viewing and validating certificates installed in a SQL Server instance.
  • Identifying which certificates may be close to expiring.
  • Deploying certificates across Always On Availability Group machines from the node holding the primary replica.
  • Deploying certificates across machines participating in an Always On failover cluster instance from the active node.

Note: You can use certificate management in SQL Server Configuration Manager with lower versions of SQL Server, starting with SQL Server 2008.

One of our customers from the USA has successfully installed SecureNT Intranet SSL Certificate on SQL Server.

Note: During the certificate installation, the regular PFX file gives mutliple errors. Contact for obtaining the correct PFX file.


Microsoft SQL server 2019 Configuration Manager

To install a certificate for a single SQL Server instance

  1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.
  2. Right-click Protocols for <instance Name>, and then select Properties.
  3. Choose the Certificate tab, and then select Import.
  4. Select Browse and then select the certificate file.
  5. Select Next to validate the certificate. If there are no errors, select Next to import the certificate to the local instance.

Configuring SQL Server to accept encrypted connections

You can configure SSL using the SQL Server Configuration Manager. First, you should run SQL Server Configuration Manager under the SQL Server service account. The only exception is if the service is running as LocalSystem, NetworkService, or LocalService, in this case, you can use an administrative account.

  1. Expand SQL Server Network Configuration and right-click on Protocols for <YourMSSQLServer>, then click Properties.
  2. On the Certificate tab, select the certificate you would like to use.
  3. On the Flags tab, select Yes in the ForceEncryption box, then click OK.
  4. Restart the SQL Server service.

Configuring the SQL Server clients to use encrypted connections

You should export the certificate from your SQL Server and install it on the client computer to establish the encryption.

  1. Open the MMC Certificates Snap-in as described above.
  2. Right-click the Certificate, point to All Tasks and then click Export.
  3. Complete the Certificate Export Wizard, storing the certificate file in a selected location.
  4. Copy the certificate to the client computer.
  5. Use the MMC Certificates Snap-in on the client computer to install the exported certificate file.
  6. In the SQL Server Configuration Manager right-click SQL Server Native Client Configuration, and then click Properties.
  7. On the Flags tab, select Yes in the ForceEncryption box, then click OK.

You can also encrypt the connection from SQL Server Management Studio:

  1. Click Options in the Connect to Server dialog.
  2. On the Connection Properties tab, tick the Encrypt connection checkbox.


  1. How to configure SSL encryption in SQL Server 2008 R2 (
  2. Certificate Management in SQL Server 2017 and 2019 (
  3. Certificate Management (SQL Server Configuration Manager) – SQL Server 2019 | Microsoft Docs
How to configure SSL encryption in SQL Server
Tagged on:                                                         

Leave a Reply

Your email address will not be published. Required fields are marked *