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

Database Requirements

Observe the following requirements and limitations for supporting Oracle GoldenGate:

  • Only user databases are supported for capture and delivery.

  • Ensure that Auto Create Statistics and Auto Update Statistics are enabled for the database.

  • The database must be set to the compatibility level of the SQL Server instance version.

  • Oracle GoldenGate supports SQL Server databases configured with Transparent Data Encryption (TDE).

  • (Extract) The source database can be set to any recovery model that supports the change data capture feature in Microsoft SQL Server.

  • If the source database was created by restoring a backup from a different instance you must synchronize the database owner SID with the SID on the new instance. Alternatively, you can use sp_changedbowner to set the restored database to a current login.

  • (AlwaysOn) Extract supports capturing from the primary database, or a read-only, synchronous-commit mode. Asynchronous-commit mode are not supported for capture.

  • Replicat performance consideration: Beginning with SQL Server 2016, Microsoft changed the default setting for the database option TARGET_RECOVERY_TIME from 0 to 60 seconds. It has been demonstrated in internal testing that this can reduce the Replicat's throughput. If you experience Replicat throughput degradation, consider adjusting the TARGET_RECOVERY_TIME setting to 0.

Limitations:

  • Oracle GoldenGate does not support capture or delivery of system databases.

  • Oracle GoldenGate does not support capture from contained databases.

  • Source database names cannot exceed 121 characters. This limitation is due to the SQL Server stored procedures that are used to enable supplemental logging.

  • If you are configuring the Oracle GoldenGate heartbeat functionality, the SQL Server database name must not exceed 107 characters.

  • Capture from SQL Server databases enabled with In-Memory OLTP (in-memory optimization) is not supported. When you add a Memory Optimized Data file group to your database, Oracle GoldenGate is not allowed to enable supplemental logging for any table in the database. Conversely, if supplemental logging has been enabled for any table in the database prior to the creation of a Memory Optimized Data file group, SQL Server does not allow a Memory Optimized Data file group to be created.

  • (AlwaysOn) Capture from databases configured in asynchronous-commit mode of an AlwaysOn Availability group are not supported.