Connecting to MySQL

Integrating your MySQL database with Alooma is easy:

  1. How do you want to connect to Alooma? If it's via an SSH server, check out how to connect via SSH. Otherwise, you'll need to whitelist access to Alooma's IP addresses.

  2. From the Plumbing screen, click Add new input. Select MySQL from the list of inputs.

  3. Name your MySQL input and enter the following details:

    • Hostname of the MySQL server (default port is 3306)

    • Username and Password (if you're using RDS/Aurora you created this when you configured CDC)

  4. If your MySQL server is behind an SSH server you can connect to MySQL via SSH.

  5. Click Connect to Continue.

  6. Select the destination schema. This is the schema where you’d like Alooma to create the tables for this input in your data destination.

  7. Choose the replication method you'd like to use for MySQL replication.


    Alooma does not support GTID replication.


    You must set up CDC prior to this step. See the corresponding "Setting up CDC" documentation for your environment.

    For CDC replication (recommended) Alooma will replicate all tables from all databases by default. If you want to load a subset of the tables in your MySQL instance, select "Specific tables from specific databases" and then click in the Table Names field and choose tables from the list that appears.

    Mark the checkbox if you want to perform an initial snapshot of historical data. If unchecked, we’ll only pull newly changed data and will not replicate any historical data.

    Q: What happens to data already replicated when a user removes a table from the list of tables to replicate?

    A: Nothing. The data remains in the data destination.

    Q: What happens when user adds a table to the list of tables to replicate?

    A: Alooma will start replicating it, and if "Perform initial snapshot" is checked, we will also dump its historical data.

    Q: What happens if users toggles "Perform initial snapshot" after replication started?

    A: Tables already being replicated are not impacted. Only tables added to the list going forward will be impacted by this change.

    For incremental replication, provide:

    • The database/schema you want to replicate.

    • A table and update indicator column (updated_at) pair for each table you want to replicate. You should also index the indicator columns. 

    Follow the instructions for creating an index here:

    For full dump/load replication:

    • Specify the database/schema you want to replicate.

    • Select the tables you want to replicate from the list.

    • Specify the frequency at which you'd like to replicate your tables. The more frequent, the more fresh your data will be, but the more load it puts on your MySQL database.

Keep the mapping mode to the default of OneClick if you'd like Alooma to automatically map all MySQL tables exactly to your data destination. Otherwise, they'll have to be mapped manually from the Mapper screen.

Alooma maintains three tables in your data destination per each table in MySQL.

That's it! You're done integrating MySQL and Alooma.

Search results

    No results found