PowerExchange can capture change data from SQL Server distribution databases for which Transparent Data Encryption (TDE) is enabled. No special configuration tasks are required.

PowerExchange does not capture change data for SQL Server system tables.

The maximum length of a row for which PowerExchange can capture and process change data is 128,000 bytes.

PowerExchange does not capture the user ID that is associated with the original transaction that updated the database.

The timestamp that PowerExchange records for each captured change indicates when the change was captured, not when the original transaction occurred.

PowerExchange does not capture change data for derived columns that are not persisted. SQL Server computes values for these columns at run-time based on an expression but does not store the values in a table.

SQL Server publishes

deferred updates

to SQL Server tables as DELETEs followed by INSERTs rather than as UPDATEs. Consequently, PowerExchange propagates deferred updates as DELETEs followed by INSERTs, even if you select

AI

for the

Image Type

attribute in the CDC connection. PowerExchange does not include before image (BI) and change indicator (CI) information in DELETE and INSERT records. If you must capture a deferred update as an UPDATE for business reasons, set the SQL Server 8207 trace flag. This flag causes the SQL Server Replication Log Reader to combine the DELETE and INSERT pair into a single UPDATE. For more information about SQL Server processing of deferred updates and the SQL Server 8207 trace flag, see the SQL Server documentation

PowerExchange does not support the use of local aliases when connecting to SQL Server and creating publications at registration creation.

If you need to switch the status of multiple SQL Server capture registrations from active to inactive or from inactive to active, use the DTLUCBRG utility with the MSSOPTS UPDATESTATUS parameter. This optional parameter enables you to switch the status of many registrations in one operation and regenerate the associated SQL Server publications.

You can run the PowerExchange Listener on a Windows system other than the Windows system where the SQL Server source distribution database runs. On the PowerExchange Listener system, you must install the Microsoft SQL Server Native Client and define a MSQL CAPI CONNECTION statement that provides connection information for the SQL Server source distribution database in the dbmover configuration file. Also, in the dbmover configuration files on the PowerCenter Integration Service machine and on the PowerExchange Navigation system, define a NODE statement that points to the PowerExchange Listener system.