MS SQL server CDC limitations - Connect_CDC - connect_cdc_mimix_share - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
ft:locale
en-US
Product name
Connect CDC
ft:title
Connect CDC Getting Started Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2026-02-25
ft:lastPublication
2026-02-25T19:01:02.274000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Connect
L4_Investment_Segment
Application Data Integration
L5_Product_Group
ADI - Connect
L6_Product_Name
Connect CDC
Changes in this topic Description
Updated in version 6.0.04.02 Support was discontinued for SQL Server 2012 (32 or 64 bit) and R2.

The following list describes the constraints or limitations of using MS SQL Server CDC:

  • By default, MS SQL Server CDC only captures Large objects (LOB) data to a maximum size of 65536 bytes. When you replicate LOB data with CDC, you cannot exceed this size. If a LOB data value is encountered that is larger than this size, the source table operation fails. If LOB data values exceed this size, you can increase the limit by configuring the max text repl size parameter in MS SQL Server. For details on how to configure this parameter, see Server configuration.

    Note:  LOB column types include TEXT, NTEXT, IMAGE, XML, VARCHAR(MAX), NVARCHAR(MAX) and VARBINARY(MAX).
  • A MS SQL Server database can not be replicated using multiple models.

  • Only available on the Enterprise, Developer editions of MS SQL Server 2014 or higher.

  • Does not support bi-directional replication.

  • You cannot truncate tables that are being captured by CDC.

  • You cannot use CDC if you are using CDC for some other application on the same server.

  • Transactional integrity will be limited to the database level.

  • Transaction username is unavailable.

  • Connect CDC does not support replication requests that contain tables from more than one MS SQL Server database.