The DBMOVER configuration file includes the following changed statement:
CAPI_CONNECTION=(NAME=
capi_connection_name
,TYPE=(MSQL,...[LOCKAVOIDANCE=
{N|Y}]))
New
. The LOCKAVOIDANCE parameter in the MSQL CAPI_CONNECTION statement controls whether PowerExchange SELECT statements use the NOLOCK hint when querying the SQL Server distribution database for change data. The NOLOCK hint can avoid lock contention with SQL Server utilities but might cause PowerExchange to miss some change records. Options are:
N
. PowerExchange SELECT queries that retrieve data from the distribution database do not use the NOLOCK hint. If locks are held on some change records, PowerExchange queries cannot retrieve the data until the locks are released. With this setting, PowerExchange queries might take longer to complete. However, no changes are skipped and data integrity is preserved. Use this option only when the MULTIPUB parameter is set to Y.
Y
. PowerExchange SQL SELECT queries that retrieve data from the distribution database use the NOLOCK hint. Use this option only when the MULTIPUB parameter is set to N. If the MULTIPUB parameter is set to Y, SQL Server might use allocation order scans to retrieve data for PowerExchange queries, which can result in missed change data and data corruption.
Instead of using LOCKAVOIDANCE=Y, Informatica recommends that you set the isolation level for the distribution database to READ_COMMITTED_SNAPSHOT ON to avoid data integrity problems.
Default is
N
if MULTIPUB is set to Y, or
Y
if MULTIPUB is set to N.
For more information, see the "DBMOVER Configuration File" chapter in the