Overview
Replicate Preview supports structured data replication between MySQL and other supported systems, allowing it to operate as both a source and target endpoint. By configuring connections and selecting required datasets, users can establish replication pipelines that ensure controlled and consistent data delivery. The platform manages execution and resource handling, simplifying deployment across MySQL environments.
Note
MySQL is currently supported as both a source and target endpoint in Replicate Preview, limited to Snapshot (full load) replication mode, with Change Data Capture (CDC) and streaming replication not yet supported.
User Permissions
Using MySQL as source connection
The following are the user permissions required using MySQL as source in Snapshot mode:
Authority to connect a database
Authority to select tables
CREATE USER <replicate_user> WITH PASSWORD 'your_password';
GRANT CONNECT ON DATABASE your_database TO 'username'@'%';
GRANT SELECT ON ALL TABLES IN SCHEMA <schema_name> TO 'username'@'%';Note
The '%' includes the IP from which the user is connecting.
Using MySQL as target connection
The user performing operations should have the following MySQL permissions:
CONNECT: Required to connect to the database.
USAGE on Schemas: Grants access to specific schemas where tables are located.
SELECT on Tables: Only used when tables already exist on the target catalog.
INSERT/UPDATE/DELETE/DROP: If changes to data or loading back are needed, these privileges are also required on the target tables.
CREATE USER your_user WITH PASSWORD 'your_password';
GRANT CONNECT ON DATABASE your_database TO 'your_username'@'%';
GRANT USAGE ON SCHEMA your_schema TO 'your_username'@'%';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP ON ALL TABLES IN SCHEMA your_schema TO 'your_username'@'%';Connection Considerations
If you do not have a connection configured, refer to Connecting to MySQL for step-by-step instructions:
When configuring and using a connection to MySQL, consider the following:
Configuration | Details |
|---|---|
Connection Parameters | Ensure that all required connection properties are correctly defined, including hostname, port (default: 3306), database name, username, and password. Incorrect values are a common cause of connection failures. |
Schema Access and Search Path | Ensure that the user has access to the required schemas and that the correct schema is referenced. MySQL environments with multiple schemas may require explicit schema qualification to avoid object resolution issues. |
Network Connectivity and Access Control | Confirm that the MySQL server is accessible from the service. Verify firewall rules, security groups, or cloud network configurations (for example, AWS Security Groups or Azure NSGs) allow inbound connections. |
SSL/TLS Configuration | If SSL is required, ensure that the MySQL server is configured to accept secure connections and that the appropriate SSL mode is selected in the connection settings. |
Large Table and Performance Considerations | For large datasets, consider query performance, indexing, and system resource utilization. Scheduling replication during low-usage periods can help reduce impact on the source system. |
Next Steps
In Replicate Preview, configure your workspace using this system datastore and start replicating data. Refer to Configure Workspace: Datastores for more information.