Home / Repstance User Guide / SUPPORTED DATABASE REQUIREMENTS

SUPPORTED DATABASE REQUIREMENTS

The privileges that the database login needs are described in Database Privileges.

Editions

Repstance is delivered in two editions: Repstance and Repstance Advanced Edition (see Getting Started with Repstance). Both support SQL Server and Oracle as a Source and as a Target. Repstance Advanced Edition also supports PostgreSQL, MySQL, Snowflake, Redshift, AWS S3 and Apache Kafka as a Target. Apache Kafka as a Target, and PostgreSQL and MySQL as Sources, are available since version 6. PostgreSQL (including Amazon Aurora PostgreSQL) and MySQL are supported as Sources in Repstance Advanced Edition only. With Repstance (not the Advanced Edition) an Apply Process for these databases does not run; it reports “[postgresql] DB is not supported”, with the name of the database type in the brackets. The databases that are enabled in the on-premises edition depend on its license key; contact support.

 

DatabaseSourceTargetEdition
SQL ServerYesYesRepstance and Repstance Advanced Edition
OracleYesYesRepstance and Repstance Advanced Edition
PostgreSQL, Aurora PostgreSQLYes, since version 6, Advanced Edition only (PostgreSQL 12 or later, including Aurora PostgreSQL)YesRepstance Advanced Edition
MySQL, Aurora MySQL, MariaDBYes, since version 6, Advanced Edition only (MySQL 8.0 or later, not MariaDB; Aurora MySQL has not been tested as a Source)YesRepstance Advanced Edition
SnowflakeNoYesRepstance Advanced Edition
RedshiftNoYesRepstance Advanced Edition
AWS S3NoYesRepstance Advanced Edition
Apache KafkaNoYes, since version 6Repstance Advanced Edition

 

 

SQL Server  

Currently, Repstance supports versions of Microsoft SQL Server that permit the use of CDC (Change Data Capture) as a Source Database with the following limitations: 

  • System databases are not supported,
  • No Contained databases are supported,
  • No databases enabled with In-Memory Optimization (2014/2016 feature) are currently supported,
  • Database Compatibility level must be 100 or higher,
  • Asynchronous AlwaysOn databases are not supported,
  • The SQL Server Agent must be running.

Any SQL Server databases starting 2008, including RDS and Azure SQL Server instances, are supported as a Target Database.

Amazon RDS for SQL Server, Azure SQL Database, Azure SQL Managed Instance and Google Cloud SQL for SQL Server are supported for Source and/or Target Databases.

SQL Server Agent is needed only where the server has one (SQL Server, Amazon RDS, Azure SQL Managed Instance). Azure SQL Database and Google Cloud SQL do not give Repstance access to the Agent. Repstance detects this when you prepare the database and when the Capture Process starts (msdb.dbo.sysjobs cannot be read), and handles the database as a PaaS database: no SQL Server Agent jobs are created or checked, and the Capture Process itself runs the heartbeat (every 60 seconds) and the housekeeping (every 30 minutes).

If the server has the Agent but the login cannot read msdb, the database is also handled as a PaaS database and the log shows a warning. Give the login the role SQLAgentUserRole of msdb and prepare the database again.

Prepare database enables CDC with the procedure of the platform: rds_cdc_enable_db on Amazon RDS, gcloudsql_cdc_enable_db on Google Cloud SQL, sp_cdc_enable_db elsewhere.

Oracle 

Repstance supports Oracle versions 10g through 19c including RAC configuration as Source and/or Target Database. Both EC2 and RDS instances are supported. 

The Oracle Source Database must be configured to run in ARCHIVELOG mode prior to use. It is recommended practice to ensure that the archive logs are not “cleaned-up” until they are processed by the Repstance Server. At least the “minimal supplemental logging” needs to be enabled either prior to use or as a part of “prepare database” command.

PostgreSQL  

Repstance supports PostgreSQL as a Target Database. The following versions are supported as a Target: 

  • PostgreSQL versions 11 through 16
  • Aurora PostgreSQL, compatible with PostgreSQL 11 through 16.

PostgreSQL, including Amazon Aurora PostgreSQL, is supported as a Source Database since version 6, by Repstance Advanced Edition only (see PostgreSQL as Source): PostgreSQL 12 or later, with wal_level = logical (on Amazon RDS: rds.logical_replication = 1, which needs a restart), a free replication slot and WAL sender, and a login that can use the replication protocol (the attribute REPLICATION; on Amazon RDS the role rds_replication).

MySQL 

The product supports MySQL as a Target Database. The following versions are supported as a Target: 

  • MySQL version 5.7
  • MySQL 8.0, including 8.0.42
  • Aurora MySQL
  • MariaDB versions 10.5 through 10.11

MySQL is supported as a Source Database since version 6, by Repstance Advanced Edition only (see MySQL as Source): MySQL 8.0 or later (MariaDB is supported as a Target only), with the binary log on (log_bin = ON; on Amazon RDS a backup retention period of 1 day or more), binlog_format = ROW, binlog_row_image = FULL and binlog_row_metadata = FULL.

Snowflake 

The product supports Snowflake as a Target Database only.

Redshift 

The product supports Redshift as a Target Database only.

AWS S3

The product supports AWS S3 as a Target only. The files are written in CSV (comma-separated values) or Parquet format, plain or compressed with gzip (see AWS S3 Apply Parameters).

Apache Kafka

The product supports Apache Kafka as a Target only, since version 6. The Apply Process publishes the changes of the Source Database as JSON messages to the topics of the cluster, one topic for every table (see Kafka as Target, Kafka Apply Parameters and Replication to Apache Kafka). It was tested with Apache Kafka 4.3 in KRaft mode. It connects with the Kafka protocol, with or without TLS, and logs in with PLAIN, SCRAM-SHA-256 or SCRAM-SHA-512.