Microsoft SQL Server CDC Connector

Microsoft SQL Server CDC Connector

CDC connection overrides

CDC connection overrides

The following table lists the connection overrides that the
Data Integration
CDC connectors support.
Connection Override
Description
Application Name
Uniquely identifies the GMD application.
CAPI Connection Name
A name that overrides the default CAPI connection name.
Compression
Specifies whether or not to compress source data. Valid values are:
  • Y.
  • N.
Default is N.
Continuous Extraction
Valid values are:
  • 0. Stop extraction at the end of the log.
  • 1. Perform continuous extraction.
Default is 0.
Encrypt Level
Specifies the encryption level to use. Valid values are: 1. AES 128, 2. AES 192, and 3. AES 256.
Default is 1.
You must specify both the Encryption and the Encrypt Level.
Encryption
Specifies the encryption to use. Valid values are: AES
This attribute has no default.
You must specify both Encryption and Encrypt Level.
Event Table
The source event table.
Log PWX Messages
Controls whether Data Integration writes informational messages related to a CDC session in the session log. Valid values are:
  • Y.
  • N.
Default is Y.
Maximum Rows Per Commit
The maximum number of change records that Data Integration processes before it sends a commit request to commit data to all targets in the CDC session. Data Integration does not wait for a UOW boundary to commit the change data.
Valid values are: 0 to 999999999.
Default is 0.
The Real-time Flush Latency in milliseconds, Maximum Rows Per Commit, and Minimum Rows Per Commit attributes work together to control commit frequency.
Minimum Rows Per Commit
The minimum number of change records that the PowerExchange Listener must read from the change stream before it passes a commit record to the target. Before reaching this minimum, the PowerExchange Listener passes only change records to Data Integration and discards any commit records.
Valid values are: 0 to 999999999.
Default is 0.
The Real-time Flush Latency in milliseconds, Maximum Rows Per Commit, and Minimum Rows Per Commit attributes work together to control commit frequency.
Number of Runs to Keep RestartToken File
The maximum number of backup copies to keep of the restart token file. Valid values are: 0 to 9999.
Default is 0.
Pacing Size
Specifies the pacing size. Valid values are: 0 to 999999999.
Default is 0.
Pacing Unit
Specifies whether to represent the pacing size in number of rows. Valid values are:
  • Y.
  • N.
Default is Y.
Password
A password for the specified user or a valid passphrase.
Real-time Flush Latency in Milli-Seconds
The number of milliseconds that must elapse before Data Integration sends a commit request to commit data to all targets in the CDC session. When this period elapses, Data Integration continues to read the changes in the current UOW until it reaches the end of the UOW. Then Data Integration sends a commit request so that the data can be committed to the targets.
Valid values are: 0 to 999999999.
Default is 0.
The Real-time Flush Latency in milliseconds, Maximum Rows Per Commit, and Minimum Rows Per Commit attributes work together to control commit frequency.
Recovery Cache Folder
The name of the file cache folder that is used for recovery of the session.
Default is
$PMRootDir/Cache
.
Replace Low-values With Spaces
Controls whether to convert character fields to string fields so that embedded nulls in data are processed as spaces. Valid values are:
  • Y.
  • N.
Default is N.
RestartToken File Name
Fully qualified restart file name.
UOW Count
The number of units of work (UOWs) that Data Integration processes before it sends a commit request to commit data to all targets in the CDC session. Valid values are: 1 to 999999999.
Default is 1.
Update As Delete/Insert
Indicates whether Data Integration should send captured Updates as Updates, or as Deletes followed by Inserts. Valid values are:
  • AI. Process Updates as update operations.
  • BA. Process Updates as Deletes followed by Inserts.
Default is AI.
User Name
A user name for connecting to the database.

0 COMMENTS

We’d like to hear from you!