1. Oracle GoldenGate Classic Architecture Documentation
  2. Prepare
  3. Prepare Your Database for Oracle GoldenGate Classic Architecture
  4. SQL Server
  5. Database Connectivity

Database Connectivity

Oracle GoldenGate uses ODBC and OLE DB to connect to a database:

  • ODBC: The Extract process uses ODBC to connect to a source SQL Server database to obtain metadata and perform other process queries. The Replicat process uses ODBC to connect to a target SQL Server database to obtain metadata, but can optionally use it for its delivery of transactions as well. ODBC must be properly configured.

  • OLE DB: By default, the Replicat process attempts to use OLE DB to connect to a target SQL Server database to perform DML operations. If the driver used only supports ODBC, then the Replicat will apply DML via ODBC. To use OLE DB in an ODBC-only driver, install the Microsoft OLE DB Driver 18 for SQL Server. Using OLE DB allows the use of the DBOPTIONS USEREPLICATIONUSER parameter, which supports the Not for Replication flag of certain table properties.

  • Using the Microsoft SQL Server Native Client 11 OLE DB driver to connect to a SQL Server 2014 instance in OLEDB mode may lead to a memory leak issue (Microsoft article 2881661). Microsoft has provided a fix in SQL Server 2014 CU1 (Microsoft article 2931693). To avoid a possible memory leak, you may choose one of the following options:

    • For SQL Server 2014, upgrade the SQL Server instance to at least Cumulative Update 1.

    • Use a Microsoft supported ODBC driver.

  • For Azure SQL Database, use a Microsoft supported ODBC driver.

  • Always On availability group listeners are supported and are required to support read-only routing for capture against a synchronous mode secondary replica.