In addition to the defect fixes announced for 126.96.36.199-5069, a number of enhancements were also made available in this build.
IIDR 188.8.131.52-5069 for Db2
IIDR 184.108.40.206-5069 for Db2 introduces two enhancements - improved database connection options for Db2 LUW databases, and mirror bulk apply for IIAS databases.
Improved database connection options (Type 4)
IIDR CDC for Db2 now provides you with the option to use Type 4 JDBC connections as the method by which the replication engine connects to Db2.
What are the benefits of using Type 4?
- For remote databases, you no longer need to catalog the database prior to refresh (using JDBC method).
- When a database is SSL-enabled, you can configure JDBC Type4 advanced parameters to have all CDC connections to the database secured.
- Using Type4, you can leverage Db2 features such as WLB (Work Load Balancing) used by PureScale databases.
For more information, please see Adding an instance of the CDC Replication Engine for Db2 for LUW (Windows)
Please note that CDC uses only native connections for Source capture (reading database logs using db2readlog api) and Fast load (db2load) Apply as db2readlog and db2load apis require native connections. But for any Db2 metadata queries Type4 connections can be used.
Mirror bulk apply
IIDR CDC for Db2 now offers mirror bulk apply (MBA) for IBM Integrated Analytics System targets, providing up to 100x RPS throughput over Fast Apply and up to 150x RPS throughput over standard JDBC apply.
What is it?
IIDR CDC provides support to Db2 Warehouse/on Cloud and IBM Integrated Analytics System (IIAS) targets. Mirror bulk apply is a new way to apply to IIAS databases that employs the external table feature available for IIAS. You can configure it using user exits in a similar fashion to IIDR CDC fast apply.
The workload consists of Insert Update and Delete operations with apply threads set to 3, latency threshold set to 60 seconds, commit size set to 100 transactions and 410mb of transaction length. In this test we used mirror bulk apply with External Table. The IIAS box is "network near" or in other words, with minimum number of hops. The test uses JDBC type 4 connection, another new feature available in IIDR CDC v220.127.116.11-5069.
Below is a graph of the throughput using Mirror bulk apply along with a comparison with Fast apply and standard CDC apply.
The above test is performed in a controlled/development environment the results shown only for reference and the results may vary in actual environments like production.
For more information, please see External table mirror bulk apply .
IIDR 18.104.22.168-5069 for Microsoft SqlServer
Remote source for the CDC Replication Engine for Microsoft SqlServer
IIDR CDC for Microsoft SqlServer now offers you the option to configure a replication engine that is remote from the source database, where the CDC engine does not have direct access to the database's transaction logs. This allows you to install CDC on a separate system from the Microsoft SqlServer database, allowing better resource management and access control.
This version of CDC for Microsoft SqlServer supports several configurations where you can run IBM CDC for Microsoft SQL Server replication engine as a source datastore on a remote system from the SqlServer database, using:
- a script to copy transaction log backups to the replication engine; or,
- a shared directory containing transaction logs; or
- an alternate location for transaction logs than the location used to back up the logs.
For more information, please see Configuring a remote source of the CDC Replication Engine for Microsoft SQL Server.
In addition, IIDR CDC for Microsoft SqlServer has reduced the privileges needed to operate a source datastore. It is no longer necessary for the CDC instance user to be granted the sysadmin role, or to be the owner of a trusted database. Now, the CDC instance user only needs to be granted the database ownership role plus several other statements. IIDR CDC for Microsoft SqlServer comes with sample scripts, grantuser-sql-nosa.sql and enablerepl-sql-nosa.sql, for granting these privileges.
For further details, please see Required database, user accounts, and schemas.