Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange CDC Introduction
  3. Part 2: PowerExchange CDC Components
  4. Part 3: PowerExchange CDC Data Sources
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

Configuring SQL Server for CDC

Configuring SQL Server for CDC

You must perform a few configuration tasks to prepare SQL Server for PowerExchange change data capture (CDC).
If your SQL Server tables have a high level of update activity, use a distributed server as the host of the distribution database from which to capture change data. This practice prevents competition between PowerExchange CDC and your production database for CPU use and disk storage.
  1. Start the SQL Server Agent and Log Reader Agent if they are not running. For more information, see your Microsoft SQL Server documentation.
  2. Verify that each source table that you want to register for change capture has a primary key.
Also, transactional replication must be enabled on the publication database. Normally, transactional replication is enabled the first time any table in the database is registered for change data capture. Each time you register an additional table, PowerExchange checks that transactional replication is still enabled and, if necessary, re-enables it. You can configure transactional replication settings in SQL Server as needed.
The default transactional retention period at the Distributor is 72 hours. If you are using the PowerExchange Logger, accept this default retention period. If you are not using the PowerExchange Logger, Informatica recommends that you increase the retention period to 14 days. However, you might need to decrease the value if you have a high volume of transactions or space constraints. For more information, see your Microsoft SQL Server documentation.

0 COMMENTS

We’d like to hear from you!