MySQL Load Mode Guide
Use this page when MySQL is the source for a Load workflow.
Load mode reads table data directly from the source. It does not require binlog setup. For background on Load mode, see Load Mode.
If you need continuous change capture, use MySQL CDC Source Configuration instead.
Source requirements
The source user needs:
- network reachability from the DBConvert Streams deployment
SELECTaccess to the source tables- SSL/TLS settings when required by the environment
No additional server-side configuration is needed — Load reads tables directly.
Example grant:
GRANT SELECT ON database_name.* TO 'user'@'%';
For connection and network setup, see MySQL Server Configuration. To verify which tables are visible with the current privileges, open the connection in Data Explorer.
Configuration flow
- Create the MySQL connection and test it from the Data Explorer sidebar (right-click → Test connection) or from the connection editor.
- Open the database in Data Explorer to confirm visible tables.
- In the stream wizard, select Conversion as the transfer mode.
- Select the tables to transfer — pick individual tables or click All to select all.
- Data Filter (per table) — select specific columns, set a row limit, add a WHERE filter, or define sort order.
- Custom SQL — use custom queries when you need full control over the extraction.
- Configure target settings — structure options, schema policy, and write mode.
- Start the stream.
Load creates tables, indexes, and constraints on the target if they are missing. Control this with structure options.
Load also supports multi-source streams — combining data from several MySQL, PostgreSQL, or file connections in a single transfer.
Cloud-hosted MySQL sources
If the source is provider-managed, use the provider page for network and service-specific details:
- Amazon RDS for MySQL Guide
- AWS Aurora MySQL Guide
- Google Cloud SQL Connection Guide
- Azure Database Connection Guide
Before starting
- If using custom SQL queries, verify them in the SQL Console first.
- Start with a narrow scope (one or two tables) before scaling up.