MySQL is an open source relational database that powers many applications and is one of the most popular databases in the world. By using MySQL as a data destination on the Kondado platform, you can create your Data Warehouse using both MySQL and MariaDB.
To automate the ETL for your MySQL Data Warehouse with Kondado, follow the steps below:
3) Name your destination and fill in your database information:
Address: Use the IP or DNS of your database for external access
Port: Fill in the port to be used for access (usually 3306)
Database: fill in the name of the database
User: database access user. This user must have DROP, INSERT, CREATE, ALTER, SELECT, DELETE, and PROCESS privileges
Password: User access password to the database
ATTENTION
a) The sql_require_primary_key parameter must be disabled – it is common for clouds like Digital Ocean to leave it enabled
b) Settings such as STRICT_TRANS_TABLES that require values in all columns (default value constraint) must be disabled
Now you can save your data destination and start using MySQL as your Data Warehouse.
Add MySQL as a Data Destination on Kondado
Configure MySQL or MariaDB as your Data Warehouse destination on the Kondado platform by releasing IPs and entering your database credentials.
Release Kondado IPs on your database server
Allow Kondado's IP addresses through your database server firewall (and VPC) on the MySQL port, typically 3306. This secure network access is required before connecting to the Kondado platform.
Navigate to add new destinations on Kondado
On the Kondado platform, go to the add new destinations page and select the MySQL data destination to begin configuring your data destination.
Name your destination and enter database details
Provide a name for your destination, then fill in the Address (IP or DNS for external access), Port (usually 3306), Database name, User, and Password for your MySQL instance.
Verify required user privileges
Ensure your database user has the necessary privileges: DROP, INSERT, CREATE, ALTER, SELECT, DELETE, and PROCESS. Without these, Kondado cannot properly manage your Data Warehouse tables.
Disable restrictive MySQL parameters
Turn off sql_require_primary_key (commonly enabled on Digital Ocean) and disable STRICT_TRANS_TABLES or similar settings that enforce default value constraints on all columns.
Save and start using MySQL as your Data Warehouse
After completing the configuration, save your destination. You can now automate ETL pipelines to MySQL and connect visualization tools like Looker Studio or Power BI to analyze your data.
