Azure MySQL (Edge)

Last updated on Dec 13, 2024

Edge Pipeline is currently available under Early Access. You can request access to evaluate and test its features.

Azure MySQL Database is an easy to set up, operate, and scale fully managed database service from Microsoft. It can automate your database management and maintenance, including routine updates, backups and security, enabling you to focusing on working with your data.

You can ingest data from your Azure MySQL database using Hevo Pipelines and replicate it to a Destination of your choice.


Data Type Mapping

Hevo maps the MySQL Source data type internally to a unified data type, referred to as the Hevo Data Type, in the table below. This data type is used to represent the Source data from all supported data types in a lossless manner.

The following table lists the supported MySQL data types and the corresponding Hevo data type to which they are mapped:

MySQL Data Type Hevo Data Type
- BIT(1)
- BOOLEAN
- TINYINT(1)
- TINYINT UNSIGNED(1)
BOOLEAN
- TINYINT(>1)
- SMALLINT
- TINYINT UNSIGNED(>1)
SHORT
- INT
- MEDIUMINT
- SMALLINT UNSIGNED
- MEDIUMINT UNSIGNED
- YEAR
INTEGER
- BIGINT
- INT UNSIGNED
- BIGINT UNSIGNED
LONG
- FLOAT(0-23) FLOAT
- REAL
- DOUBLE
- FLOAT(24-53)
DOUBLE
- NUMERIC
- DECIMAL
DECIMAL
- CHAR
- VARCHAR
- TINYTEXT
- TEXT
- MEDIUMTEXT
- LONGTEXT
- JSON
- ENUM
- SET
VARCHAR
- TIMESTAMP TIME_TZ
- DATE DATE
- TIME TIME
- DATETIME TIMESTAMP
- BIT(>1)
- BINARY
- VARBINARY
- TINYBLOB
- BLOB
- MEDIUMBLOB
- LONGBLOB
BYTEARRAY

At this time, the following MySQL data types are not supported by Hevo:

  • GEOMETRY

  • LINESTRING

  • POLYGON

  • MULTIPOINT

  • MULTILINESTRING

  • MULTIPOLYGON

  • GEOMETRYCOLLECTION

  • Any other data type not listed in the table above.

Note: If any of the Source objects contain data types that are not supported by Hevo, they are marked as unsupported during object configuration in the Pipeline.


Source Considerations

  • MySQL does not generate log entries for cascading deletes. So, Hevo cannot capture these deletes for log-based Pipelines.

Limitations

  • Logging in using SSL not supported. This setting is enabled by default. You can disable it as follows:

    1. In the left navigation pane, under Settings, click Server Parameters.

    2. Under the Top tab, update the value of require_secure_transport server parameter to OFF, and then click Save.

      Disable SSL

  • Hevo only fetches tables from the MySQL database. It does not fetch other entities such as functions, stored procedures, views, and triggers.

  • Hevo does not set the metadata column __hevo_is_deleted__ to True for data deleted from the Source table using the TRUNCATE command. This action could result in a data mismatch between the Source and Destination tables.

Tell us what went wrong