Setting up Server Project with Remote HDB (SQL Server)

Scenario
You want to set up the Server project and link it up with History Database (SQL server) located on remote computer. Furthermore, you want to encrypt the communication between a Server project and the linked HDB, SQL Server located on different computers (SSL on TCP/IP connection) to establish a secured communication.

For this, you must set the encryption in the SMC located on Server and in the SQL Server Configuration Manager located on the remote Server computer. You can use a commercial certificate from Certificate Authorities (CA) or a self-signed or a SMC-created Windows Store based host certificate with a full name of the computer (host name + domain), for example, ABCXY022PC.dom01.company.net.

For background information, see the reference section.

Prerequisites

• On Server, SMC is launched and a project is restored or created and activated and started.
• The root, host certificates used for securing the communication between Server and remote SQL Server are imported in the appropriate Windows Certificate store on Server station using SMC and set as default.
• The root certificate (.cer file) is imported in the Local Computer and User Certificates > Trusted Root Certificate Authorities (TRCA) store.
• The host certificate having the full name of the remote SQL Server computer (host name + domain) must be generated using the Server root certificate and (.cer file and .pfx file) is imported in the Local Computer > Personal Store.
• On Remote SQL Server, same Server root certificate (.cer file) and the remote SQL Server host certificate (.pfx file) is available on the disk.
• Using MMC the host certificate (.pfx file) is imported in the Current User > Personal Store. See Import the Certificates in the Windows Store using MMC in Security Certificates Procedures.

Overview