You can install and run the StarQuest Data Replicator (SQDR) on:
Windows Server 2016, Server 2019, Server 2022
Windows 10 or 11 64-bit edition
Red Hat or Oracle Linux 8.x. Other Linux distributions may work.
Stelo-supplied Linux container on any Linux or other x86-based system that supports containers; this includes Windows and older versions of Linux.
A minimum screen resolution of 1024 x 768 is recommended when using Data Replicator Manager.
If you are currently running a 32-bit version of SQDR on a 64-bit operating system, you must upgrade to the 64-bit version of SQDR; see the technical document Upgrading to 64-bit SQDR for upgrade instructions or contact Stelo Support.
The Data Replicator requires a control database in which to store definitions for sources, destinations, and subscriptions. You can use either IBM Db2 for Linux, Unix Windows (Db2 LUW) or Microsoft SQL Server for the SQDR control database. For a combined tier deployment, we recommend using the version of Db2 LUW provided by Stelo (installed with SQDR Plus to enable incremental support). If you prefer to use SQL Server and do not already have a SQL Server installation, you can obtain the SQL Server Express free of charge from www.microsoft.com/downloads to use as a control database for the Data Replicator. Similarly, you can obtain Db2 Developer Community Edition free of charge from IBM. Stelo Support can assist in selecting, obtaining, and installing the DBMS software for your control database.
IBM Db2 for LUW 11.5.5 or later. Existing installations using Db2 10.5, 11.1, and 11.5.0 will continue to function, but we recommend updating to 11.5.5 as soon as possible..
SQL Server 2016/2017/2019/2022
The control database can be either local or remote. For a remote database, install the appropriate ODBC driver. For Db2 for LUW, use StarSQL (included in the SQDR installer). For SQL Server, use Microsoft ODBC Driver 17 or 18. See Using_a_Remote Control Database for details.
You can replicate data to and from any of the following database systems:
IBM Informix Dynamic Server Enterprise or Express Edition 10.0, 11.10, 11.50, 11.70, 12.10, 14.10
IBM Informix Extended Parallel Server 8.50 and higher
IBM Informix SE 7.25
IBM Informix OnLine 5.20
and higher
Incremental replication is supported from the following platforms using the separately-licensed SQDR Plus product:
Db2 for i v5r4 and later
Db2 for Linux, UNIX, and Windows v9.7 and later
SQL Server 2012 and later
Oracle 11.2 or later
Informix 11.70 or later
MySQL 5.6 or later
MariaDB
Amazon Web Services Aurora (MySQL or PostgreSQL-compatible)
Amazon Relational Database Service (RDS) for MySQL 5.6 or later
Google Cloud SQL for MySQL
PostgreSQL (including cloud implementations)
Access to Db2 databases requires the StarSQL ODBC/DRDA driver (v6.20 or later is recommended and is included in the SQDR installer), IBM Db2 ODBC Driver (DB2 Connect), IBM i Access for Windows, or IBM i Access Client Solutions.
If you use IBM i Access for Windows for accessing a Db2 for i database, install iAccess 7.1 (5770-XE1) with the SI64724 (June 2017) service pack (or later). If you use IBM i Access Client Solutions (5733XJ1), the Windows Application Package must be at the June 2017 level (or later).
For access to SQL Server, use the Microsoft ODBC 17 or 18 driver.
Access to Apache Derby (JavaDB) databases requires StarSQL 6.20 or later.
Oracle considerations:
Access to Oracle databases requires one of the following ODBC drivers:
SQDR bundled ODBC 8 driver for Oracle (recommended).
Oracle Instant Client (12.1.0.2 or later)
Full Oracle Client
Progress DataDirect Connect or Connect64 for ODBC (Oracle Database Wire Protocol Driver)
EasySoft Oracle ODBC driver.
When using Oracle as a source or destination, we recommend setting the system environment variable NLS_LANG in the system control panel to ensure proper character translation of character data to the local ANSI page of the SQDR system. For example, if you are using a US English Windows system, set NLS_LANG to AMERICAN_AMERICA.WE8MSWIN1252. This is especially important if you disable the Bind Character types as Wide (Unicode) option in the SQDR service properties dialog.
For more information about the NLS_LANG
environment variable, see:
Oracle
11g Appendix C Configuring Oracle Database Globalization Support
Oracle
12c Appendix C Configuring Oracle Database Globalization Support
When using the SQDR bundled ODBC driver for Oracle, make the following changes on the Advanced panel: supply the string ColumnSizeAsCharacter=1; ColumnsAsChar=1 in the Extended Options field.
MySQL considerations:
We recommend using Connector/ODBC 8.0.27; do not use Connector/ODBC 8.0.28 or later or 5.1.6. You can also use the SQDR bundled ODBC driver or DataDirect Connect for ODBC if you are using MySQL Enterprise.
We recommend using the Unicode (w) version rather than the ANSI (a) version of the MySQL ODBC driver when SQDR is configured for Bind Character Types as Wide (Unicode), which is the default.
If MySQL is the destination for an incremental subscription, specify the option Return matched rows instead of affected rows in the Cursors/Results panel of the MySQL ODBC configuration or specify FOUND_ROWS=1 in a connection string. This is particularly important if the MySQL database is configured as case-insensitive and the source database is not.
Enable Prepare statements on the client in the Details/Misc panel of the MySQL ODBC configuration or specify NO_SSPS=1 in a connection string to avoid an error condition in which the server exhausts its prepared statement limit.
Informix considerations:
You can use the IBM Informix ODBC driver from Client SDK v4.10FC6X2 or later (latest version recommended), the IBM Db2 ODBC driver, the SQDR bundled ODBC driver, or the DataDirect Connect for ODBC driver to connect to Informix. Some drivers may have limitations; for example, the IBM Db2 ODBC driver cannot handle variable UDT (CLOB) fields.
The SQDR bundled ODBC driver cannot connect to an Informix 14.10 server; we recommend using the latest IBM Informix ODBC driver.
PostgreSQL considerations:
When using the psqlODBC driver for PostgreSQL as a destination, we recommend configuring the Advanced panel as follows:
Max Varchar Size: 32767
Max Long Varchar Size: 214748364 (2GB)
A connection string would like this:
Servername=myhost;Database=mydatabase;Port=5432;MaxVarcharSize=32767;MaxLongVarcharSize=214748364
When using the SQDR bundled ODBC driver for PostgreSQL as a destination, we recommend configuring the Advanced panel as follows:
Enable the checkbox for Fetch TSWTZ as Timestamp (the default is to treat this type as CHAR(27))
Max char Size: 255
Max Varchar Size: 32767
Max Long Varchar Size: 214748364 (2GB)
A connection string would like this:
HostName=myhost;Database=mydatabase;PortNumber=5432;FetchTSWTZasTimestamp=1;MaxCharSize=255;MaxVarcharSize=32767;MaxLongVarcharSize=214748364
Snowflake considerations:
Issue the following command for the user being used by SQDR for the Snowflake destination:
alter user myuser set TIMESTAMP_TYPE_MAPPING = 'TIMESTAMP_LTZ'
Snowflake does not support INDEX create/drop, but does support primary key/unique index constraints.
BigQuery considerations:
If a DSN will be used instead of a connection string, then the “Enable Session” check box should be enabled on the Advance property page of the DSN Configuration
Other Drivers
In addition, you can use the Data Replicator with other databases if they can be accessed through an ODBC driver that complies with Level 2 of the ODBC 3.51 specification.
If you use an ODBC driver other than StarSQL there may be additional configuration requirements to use the driver for replications with SQDR. The SQDR Release Notes and the Stelo Info Center provide details about known issues for using SQDR with other products.