10.3.2 Azure Synapse Analytics

• About Azure Synapse Analytics Connections
  
• Before You Begin
  
• Create and Validate an Azure Synapse Analytics Connection
  
• Use an Azure Synapse Analytics Connection in Replicat
  

10.3.2.1 About Azure Synapse Analytics Connections

An Azure Synapse connection stores the information that Oracle GoldenGate DAA uses to connect to an Azure Synapse Analytics workspace. After the connection is created and validated, you can reuse it when configuring Replicat processes that replicate transactional data to Azure Synapse Analytics.

The connection stores the endpoint, authentication, security, and runtime configuration independently of the Replicat configuration. This allows multiple Replicat processes to use the same validated connection.

10.3.2.2 Before You Begin

Before creating an Azure Synapse connection, ensure that you have the following:

• An Oracle GoldenGate DAA deployment.
• Network connectivity between the Oracle GoldenGate DAA deployment and the Azure Synapse Analytics workspace.
• The Azure Synapse server name or JDBC connection URL.
• The target database name.
• A valid database user name and password.
• TLS certificates, if your deployment requires secure connectivity.
• An Azure Data Lake Storage connection: Azure Synapse Replicat requires an Azure Data Lake Storage connection to stage data before loading it into Azure Synapse Analytics. For more information, see Create and Validate an Azure Synapse Analytics Connection .
• The Azure Synapse JDBC driver and any required client libraries, if they are not already available in the deployment.

  To download the required dependencies, use the Oracle GoldenGate DAA Dependency Downloader:

  {GGforDAA install}/DependencyDownloader/synapse.sh 12.6.1.jre8

  Download the supported Microsoft SQL Server JDBC driver from:

  https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc/12.6.1.jre8

  • The Hadoop client is also required to stage data to Azure Data Lake Storage.
  • After downloading the dependencies, configure the gg.classpath property in the Java Adapter properties file to include the downloaded libraries before starting the Replicat process.
• Configure common runtime settings, such as the runtime classpath, if additional libraries are required.
• Proxy information if the deployment accesses Azure Synapse Analytics through an HTTP proxy.

10.3.2.3 Create and Validate an Azure Synapse Analytics Connection

Use the Add Connection page to create an Azure Synapse connection.

Procedure

1. In the navigation menu, select DB Connections.
2. Click Add Connection.
3. In Connection Alias, enter a unique name for the connection.
4. From Technology Type, select Azure Synapse.
5. In the Technology Settings section, provide the Azure Synapse connection information.
   • Server: Specifies the Azure Synapse Analytics server name or JDBC endpoint used to establish the connection.
   • Database: Specifies the target Azure Synapse database.
   • Username: Specifies the database user name that Oracle GoldenGate uses to connect to Azure Synapse.
   • Password: Specifies the password associated with the database user. This field is treated as sensitive information and is displayed as a password field.
6. Configure the Security Settings section.
   • Security Protocol: Specifies the security protocol used by the connection, if applicable.
   • TLS Certificate: Specifies the certificate information required to establish a secure connection when TLS is enabled.

   Note:

   Configure security properties only when required by your deployment. If TLS is not required, leave the optional security fields blank.
7. Configure Common Settings, if additional runtime configuration is required.

   Classpath: (Required) Specify the full path to client libraries are required by the replicat type. You can use Dependency Downloader to download client libraries.

8. (Optional) Configure Proxy Settings if the Oracle GoldenGate deployment accesses Azure Synapse Analytics through an HTTP proxy.
   • Proxy URL – Specifies the URL or host name of the proxy server used to access Azure Synapse Analytics.
   • Proxy Port – Specifies the port number of the proxy server.
   • Proxy Username – Specifies the user name for proxy authentication, if required.
   • Proxy Password – Specifies the password for proxy authentication. This field is treated as sensitive information.
   • Truststore – Specifies the Java truststore file that contains the certificate authority (CA) certificates used to validate the proxy server certificate, when required.
   • Truststore Password – Specifies the password associated with the truststore.
   • Keystore – Specifies the Java keystore file containing the client certificate and private key used for client authentication, when required.
   • Keystore Password – Specifies the password associated with the keystore.
   • SSL Key Password – Specifies the password protecting the private key stored in the keystore when it differs from the keystore password.

   Note:

   If the Oracle GoldenGate deployment has direct network connectivity to Azure Synapse Analytics, leave the Proxy Settings blank.
9. Click Submit.
10. On the DB Connections page, click DB Login to validate the connection.

    Note:

    A successful DB Login validates only the saved connection information. It does not validate the Replicat configuration or Azure Synapse handler configuration. After successful validation, the connection is available for selection during Replicat creation.

10.3.2.4 Use an Azure Synapse Analytics Connection in Replicat

After the Azure Synapse connection has been successfully validated:

1. Create or edit a Replicat.
2. Select Azure Synapse as the target technology.
3. Select the validated Azure Synapse connection.
4. Select the Azure Data Lake Storage (ADLS) connection required for staging data.
5. Complete the remaining Replicat configuration.
6. Create the Replicat.
7. Configure the remaining Azure Synapse-specific handler properties before starting the Replicat.

Note:

Azure Synapse Replicat requires a valid Azure Data Lake Storage (ADLS) connection for data staging. Ensure that the required ADLS connection has been created and validated before configuring the Replicat.