New features (MySQL)

MySQL connector DCT parity

MySQL connector UI and API features in Continuous Data are now fully supported in DCT, introduced in DCT 2026.3.0. This release includes support for environment creation, dSource linking, snapshot ingestion, and VDB provisions. We encourage Delphix administrators to install and migrate their day-to-day MySQL connector management to DCT. For more information, see MySQL operations in DCT.

Release 2026.3.0

This connector release supports the following feature(s):

• Reset the VDB root password during provisioning and reconfiguration

  During VDB provisioning and reconfiguration, the MySQL connector sets the VDB root password to the value configured for the vdb_pass parameter.

• Populate MySQL timezone tables during staging initialization

  The MySQL connector automatically populates the MySQL timezone tables when it initializes the staging database. Install tzdata on the staging host to enable timezone support. MariaDB staging is not supported for this feature.

• Support for SDI expanded characters

  Selective Database Ingestion (SDI) now accepts MySQL-compliant database names, including hyphens, embedded spaces, and names made up entirely of non-alphanumeric characters (for example ---). Names are validated at the input field before any backup or replication is initiated. A name is rejected if it exceeds 64 characters, is empty, begins or ends with a space, or contains /, \, ., a backtick, $, a comma, an ASCII control character, or an emoji.

  The $ is rejected even though MySQL permits it. Separate multiple names with commas and no spaces: db1,db2 is valid, db1, db2 is not.

Release 2026.2.1

This connector release consists of only bug fixes.

Release 2026.2.0

This connector release supports the following feature:

• Support for Selective Database Ingestion (SDI) for MySQL 8.0+

  The MySQL connector introduces the selective database ingestion (SDI) type that allows users to ingest specific databases from a MySQL source instead of the entire instance. The SDI is support only for MySQL 8.0 and higher. For more information, see Selective Database Ingestion page.

• Support for database user and role export

  The MySQL connector uses the SDI to automatically export and import the database users, roles, and permissions associated with the selected databases. This ensures that access control is preserved on staging databases after ingestion. For managed cloud databases (RDS/Aurora) where system tables are not accessible, the MySQL connector proceeds with database-only restoration and logs a warning.

• Enhanced replication filtering

  The MySQL connector uses REPLICATE_WILD_DO_TABLE for database-level replication filtering. This ensures data definition language (DDL) statements are replicated correctly regardless of the active database context set by USE statements.

• Improved password security

  The MySQL connector allows to pass credentials to MySQL CLI tools via the MYSQL_PWD process environment variable instead of directly on the command line. This prevents passwords from being visible in process listings.

• SDI supports integration with HashiCorp Vault for secure credential management

  When enabled, database credentials (source, staging, and replication) are fetched from the HashiCorp Vault at runtime instead of being stored in plain text. This feature is supported only for SDI.

Release 2026.1.0

This connector release supports the following feature:

• Support for MariaDB version 10.11.11 database

  The connector enhancement supports MariaDB version 10.11.11 database and ensures compatibility with the RHEL 8.10 version for the MySQL connector.

Release 2025.1.1

This connector release consists of only bug fixes.

Release 2025.1.0

This connector release supports the following feature:

• Support for MySQL v8.4 database

  The connector enhancement supports MySQL v8.4 database and ensures compatibility with the 8.4 version for the MySQL connector.

• Validate my.cnf file for snapshots created with v2025.1.0 onwards

  The connector will now validate my.cnf file for the snapshots created from v2025.1.0 onwards. The my.cnf file validation applies to new dSources, VDBs, and their snapshots created from v2025.1.0 onwards and with MySQL v 8+ databases.

• Support for upgrade from MySQL 8.0.x to MySQL 8.4

  With connector version 2025.1.0, MySQL version validation will include a three-digit check. When creating a VDB from a dSource, the MySQL version on the target environment must exactly match the dSource version, including all three version digits.

Release 4.8.2

This connector release supports the following feature:

• Enhanced connector wait time

  The connector wait time parameter is introduced to allow MySQL database to start properly and avoid the failure of execution of MySQL queries after starting the database.

• Improved the Resynchronising dSource field behaviour

  By default, the Resynchronising dSource check box is selected when creating a dSource. If the user unselects this check box during dSource creation, then an error messages appears stating "The Resynchronising dSource field should always be selected when creating a dSource. Resynchronising dSource will result in a non-incremental data load from the source database. Please select it and try again" .

Release 4.8.1

This connector release supports the following feature(s):

• Inheritance of the MySQL configuration file (my.cnf)

  • The staging database’s my.cnf configuration parameters are now recorded by the dSource and shared with the provisioned VDBs.

• Introduction of Restricted parameters during provisioning VDB

  • Restricted parameters are my.cnf parameters that are critical for Continuous Data to control for clean dataset ingestion and provisioning. The user cannot change restricted parameters. The current list of restricted parameters:

    • server-id

    • socket

    • port

    • basedir

    • data-dir

    • tmpdir

    • log-error

    • pid-file

Release 4.7.0

This connector release supports the following feature(s):

• Certification of RHEL 8.9

  • Certified MySQL and Percona v8.0 on RHEL v8.9 and lower.

Release 4.6.0

This connector release supports the following feature(s):

• Certification of Amazon Linux 2

  • The Amazon Linux 2 operating system is certified against the MySQL connector and MySQL 8.0.X.

  • This ensures that when Amazon Linux 2 is the source environment (MySQL 8.0.X) and Amazon Linux 2 (MySQL 8.0.X) is the staging environment, staging push and replication flows work as expected. Finally, VDBs can be provisioned onto Amazon Linux 2 target environments.

• Certification of MySQL RDS / MySQL RDS Aurora with Amazon Linux 2 (Staging Push) - Staging Push is certifiedwith AWS RDS and AWS RDS Aurora in AWS (PaaS) as a source and Amazon Linux 2 as a staging environment. 

• Custom backup folder for Delphix Initiated backup - By default, the /tmp folder was used to store the backup files during the Delphix initiated backup. With this release, customers can provide their backup folder with proper privileges. 

• Source Config parameters are now optional - While creating dSources with Staging Push, the installation (or Source Config) parameters are optional. However, they are required for the two replication-based linking mechanisms.

Release 4.5.0

This connector release supports the following feature(s):

• Dynamic UI: This release introduces dynamic UI changes that will make only those fields visible that are required for the selected ingestion mechanism (dSource Type) staging push or replication. As part of this feature, the following changes have been made:

  • The Database List and Logsync fields are now removed from the linking screen.

  • Provide different Replication User is added on the linking screen. This field is used in scenarios where you explicitly want to provide different replication user credentials.

Release 4.4.0

This connector release consists of only bug fixes.

Release 4.3.0

This release renames the ‘Manual Backup Ingestion’ mechanism to 'Staging Push’. You can notice this change when you create a dsource. For more information, refer to Linking using Staging Push mode.

Release 4.2.0

This connector version introduces data source sizing which enables users to calculate the size of ingested MySQL databases. For more information, refer to Source sizing implementation for MySQL dSources.

Release 4.1.0

This connector version blocks the creation, rollback, and refresh actions of VDBs on target environments when the installed MySQL version is not the same as the dSource’s installed MySQL version. This is a protective feature that prevents the accidental corruption of MySQL VDBs.

Release 4.0.0

This connector version supports MySQL v8 across all certified editions.

Release 3.0.0

This connector version has the following new feature(s):

• The MySQL connector version 3.0.0 has been enhanced for improved security and stability. We have added fixes for the following:

  • Dataset creation workflows can detect if the provided port number is already in use by an existing MySQL instance and notify the user.

  • Corrected the reported dSource and VDB statuses.

  • Fixed the Snapshot with Parameters functionality of the Manual Backup Ingestion to work smoothly and without errors.

  • Improved UI descriptions, UI and connector validations, and error messages.

• Added support for Percona Server for MySQL version 5.7 using Manual Backup Ingestion and Binary Log Replication ingestion models.

• Integrated support for MySQL and Percona Server for MySQL version 5.7 in a consolidated release stream. If you have installed divergent or custom branches of the MySQL connector you should look to migrate to this production stream. Future features and bugs will be resolved here.

• Implemented various security fixes.

Release 2.1.0

The MySQL connector 2.1.0 release consists of security improvements.

Release 2.0.26

This connector version has the following new feature(s):

• Selecting Databases: Ability to select specific databases in the Source MySQL server when creating a dSource.

• Delphix generated config file: If a my.cnf file is not provided while creating a dSource, Delphix now creates one.

• New Exit Return Codes: MySQL connector 2.0.26 introduces more granular error exit codes.