Skip to main content Skip to complementary content

Installing MS Azure SQL Managed Instance source

Before you begin

Refer to MS Azure SQL Managed Instance requirements before starting the installation.
Information noteNote: In case of an update:
  • With Talend Change Data Capture versions prior to 7.17.0, make sure all previously installed services are uninstalled. Go to DestinationPath > SQLServer and click ddUniversalSqlServer_uninstall.cmd, ScheduleSQLServer_uninstall.cmd and SPVSQLServer_uninstall.cmd.
  • Now you can delete SQLServer folder.
  • From the Registry Editor, go to HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Gammasoft\DataDistribution and delete DD_for_SQLServer folder.

Procedure

  1. Launch setup.exe and click Install > Click to install.
  2. Select SQL Server Source.
  3. Once the SQL Server Source is deployed, you need to define the fields of the Login window as follows:
    • Server: alias name, as defined in C:\windows\syswow64\cliconfg.exe tool.
    • Instance: name of the database stored in Azure SQL MI.
    • Select Azure SQL Server MI in the drop-down list.
    • User Name: user@servername, as entered in cliconfg.exe tool.
    • Password: password of the Azure account user.
    • Driver: select an ODBC driver version that is higher or equal to 17 for SQL Server.
      Information noteNote: Do not select the Native Client ODBC driver.
    • Working directory: enter the storage account that was created in your Azure account. See MS Azure SQL Managed Instance requirements for more information.
      Information noteNote: Replace all slash signs with backslash signs in the working directory URL.
    • Storage connection: if available, enter the storage connection string name that is displayed in Storage access keys from your Azure account.

Results

Talend Change Data Capture then creates and installs the elements required by MS Azure MI for SQL.

At the end of the installation, the following message is displayed: Setup was completed successfully.

Once MS Azure MI for SQL source is installed, you can check the following:
  • UseAlias parameter has been activated in the registry keys. For more information, see DD_for_SQLServer registry subkey.
  • Connection to the source database using the alias is successful.

Then launch Talend Change Data CaptureManager and subscribe to it. See Managing sources for more details.

Information noteWarning: As this Talend Change Data Capture source relies on an intermediate layer (Microsoft SQL Server CDC), the use of databases is pooled. Be careful when activating or deactivating the journalization and replication processes, as they will be shared with the other users.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here