Introduction to Microsoft SQL Server CDC Connector

SQL Server CDC Connector extracts the change records from PowerExchange Logger log files and sends the change records to Data Integration. Data Integration can then transmit the change records to a supported target.

When you define mappings in Data Integration, you select the extraction maps that PowerExchange generated for SQL Server source tables when you registered the tables. The SQL Server CDC Connector metadata adapter can then retrieve the source metadata from the extraction maps and store this information in the cloud.

To extract source change records from PowerExchange Logger log files, you must run the mapping tasks that are associated with the mappings. A mapping task runs to the end-of-log (EOL) in the PowerExchange Logger log files and then stops. You can manually restart the mapping task from a specific point in the logs, create a schedule that runs the mapping task on a recurring basis, or run the mapping task continuously. If the mapping task fails, SQL Server CDC Connector can resume processing from the point of interruption based on recovery information that is stored on the target.

SQL Server CDC Connector must be able to connect to an active PowerExchange change capture environment that includes the PowerExchange Logger. You do not need to copy the PowerExchange dbmover configuration file or PowerExchange Logger pwxccl configuration file to the SQL Server CDC Connector system. For more information about configuring PowerExchange for SQL Server CDC and the PowerExchange Logger, see the PowerExchange CDC Guide for Linux, UNIX, and Windows.

SQL Server CDC Connector works with the Informatica Cloud Secure Agent. When you install and start the Secure Agent, it downloads the SQL Server CDC Connector components and PowerExchangeClient packages. When you define a runtime environment, you configure a Secure Agent group.