Skip to main content

DD_for_SQLServer registry subkey

For each given instance of an MS SQL Server server for which Talend Change Data Capture for MS SQL Server Source has been installed, you get a key below the DD_for_SQLServer key. Its name will be the MS SQL Server instance name.

For example, if you install or add Talend Change Data Capture for an MS SQL Server instance named TCDC_DEV_DEV2 or DEV2\TCDC_DEV_DEV2 (meaning TCDC_DEV_DEV2 instance on the DEV2 server), you will get a subkey named TCDC_DEV_DEV2.

In this subkey, the following parameters will be applicable for this SQL Server instance:

Parameter Description

DriverName

This parameter contains the ODBC driver name used to access the MS SQL Server base. The default value is SQL Server.
LobManagement Used with an MS Azure SQL source to manage large objects.
  • value = 0 (default value) means LOBS are not managed
  • value = 1 means BLOBs are considered as NULL columns
  • value = 2 means BLOBs are considered as empty columns

Maxtrans

Used with an MS Azure SQL source to stop the capture of a table and move on to the next table.

  • value =0 means no limit is set. Tables are captured one by one.
  • value =1 or more means the captured rows of a table are limited to the value entered.

ParamPwd

This parameter is only available if the MS SQL Server is on 7.0 version or if the SQL instance for an MS SQL 2000 Server is not a named instance. Its value is taken into account by the unnamed instance (SQL 2000) or by the 7.0 MS SQL Server.

This parameter indicates the MS SQL Server password associated with the username (ParamUid parameter described above) that will be used by the manager, the scheduler, the supervisor and the source engine to establish the connection to MS SQL Server.

The default value is the one provided after the installation (see Installing MS SQL Server source).

ParamUid

This parameter is only available if the MS SQL Server is on 7.0 version or if the SQL instance for an MS SQL 2000 Server is not a named instance. Its value is taken into account by the unnamed instance (SQL 2000) or by the 7.0 MS SQL Server. This parameter specifies the username that will be used by the manager, the scheduler, the supervisor and the source engine to establish the connection to MS SQL Server.

The default value is the value provided after the installation (see Installing MS SQL Server source).

TextMaxLength

This parameter exists only if the MS SQL Server is on 7.0 version or if the SQL instance for an SQL 2000 server is not a named instance.

Its value contains the maximal length for a text area in case no details are provided in the DD_MX table provided during the parameter definition. This information is usually not used.

Its value is included by the unnamed instance (SQL 2000) or by the 7.0 MS SQL Server.

The default value is set to 1000 characters.

Unicode This parameter is used with an MS Azure SQL source to keep the Unicode values.
This key activates and deactivates the Unicode parameter, which manages nvarchar data type columns:
  • value= 0 (default value) means the Unicode is not activated: characters are converted to ANSI 1 byte. Unicode values are not kept; only nvarchar columns are kept.
  • value= 1 means the Unicode is activated: nvachar are stored on 2 bytes in the journal.The total length of the nvarchar table is doubled.
    Information noteNote: Issues may arise in the following case: after performing replications with Unicode = 0, you decide to change the value to 1. Before changing the value, contact Talend Support team.
UseAlias This parameter is automatically activated (default is set to 1) when an MS Azure Managed Instance for SQL source has been installed. See Installing MS Azure SQL Managed Instance source for more details.

Set the parameter to 0 if you want to stop using this source.
UseCDC This parameter is automatically activated (default is set to 1) when an MS Azure SQL source has been installed.

Set the parameter to 0 if you want to stop using this source.

WaitBeforeLog

This parameter configures the duration of the break between MS SQL Server calls.

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