Microsoft SQL Server

To add Data Source for Microsoft SQL Server:

1. Launch AVEVA Integration Service web administrator. For example, <https://integration service server host name>/.

2. Click Add Data Source.

   

3. In the Name text box, specify the name for the data source.

   Note: The data source name must be unique and must not contain special characters other than _ (underscore), - (hyphen), and space.

4. From the Product drop-down list, select the product SQL Server.

   

5. Select the authentication option from Authentication drop-down list.

   1. To connect using Windows authentication, select Windows Authentication.

   2. To connect using SQL Server Security, select SQL Server Authentication.

      

6. Provide the Server details and select the desired MDB/Database (you may have to specify the User Name and Password if authentication type is SQL Server Authentication)

   

7. Click Test Datasource.

   If all inputs provided are valid, a success message is displayed.

   

8. Click OK.

9. Click Save.

   The data source is saved, and a success message is displayed.

   

   

SQL Server Encrypted Connection

Unencrypted communication between AIS and the SQL Server database poses a security risk. Network traffic can be intercepted (sniffed), allowing an attacker to read sensitive data or manipulate database queries. To address this, AIS 4.1 can longer connect to a SQL Server if the connection is not encrypted.

This is a mandatory security requirement effective from AIS version 4.1 onwards.

Prerequisites

Before adding a SQL Server as a data source in AIS, please ensure the following steps are completed:

10. Install a Valid TLS Certificate on SQL Server

    SQL Server requires a valid TLS certificate to encrypt client connections. The certificate must meet the following criteria:

    • Issued by a trusted Certificate Authority (CA) — either a public CA or your organisation's internal CA

    • The server's Fully Qualified Domain Name (FQDN) must appear in the certificate's Subject or Subject Alternative Name (SAN)

    • Key usage must include Server Authentication

      Note: If no certificate is configured, SQL Server falls back to a self-signed certificate. While this enables encryption, it is not trusted by clients and is not recommended for production environments.

    To apply the certificate in SQL Server:

    3. Open SQL Server Configuration Manager.

    4. Right-click Protocols for [InstanceName], select Properties.

    5. Go to the Certificate tab

    6. Select the certificate from the list

    7. Click OK and restart SQL Server

11. Configure the SQL Server Connection String (Mandatory)

    Regardless of whether encryption is enforced at the server level, the client connection string must explicitly request TLS encryption.