Connecting with ODBC or Default OLE DB

If Replicat connects through the default ODBC connection or through the OLE DB connection, the following limitations apply:

  • To keep IDENTITY columns identical on source and target when using ODBC or default OLE DB, Replicat creates special operations in its transaction to ensure that the seeds are incremented on the target. These steps may reduce delivery performance.

  • You must adjust or disable triggers and constraints on the target tables to eliminate the potential for redundant operations.

To use Replicat with either ODBC or OLE DB, follow these steps:

  1. ODBC is used by default, unless the Microsoft OLE DB Driver for SQL Server is installed, in which case OLE DB is used. To force ODBC connectivity, add DBOPTIONS USEODBC to the Replicat.
  2. Disable triggers and constraints on the target tables. See Disabling Triggers and Cascade Constraints on the Target.
  3. To use IDENTITY columns in a bidirectional SQL Server configuration, define the IDENTITY columns to have an increment value equal to the number of servers in the configuration, with a different seed value for each one. For example, a two-server installation would be as follows:
    • Sys1 sets the seed value at 1 with an increment of 2.

    • Sys2 sets the seed value at 2 with an increment of 2.

    A three-server installation would be as follows:

    • Sys1 sets the seed value at 1 with an increment of 3.

    • Sys2 sets the seed value at 2 with an increment of 3.

    • Sys3 sets the seed value at 3 with an increment of 3.