MySQL support
Supported versions
Versions: 5.1, 5.5, 5.6, 5.7, 8.0
Specification
Imported metadata
Tables
| Imported | Editable | |
|---|---|---|
| Tables | ✅ | ✅ |
| Columns | ✅ | ✅ |
| Data types | ✅ | |
| Nullability | ✅ | |
| Default value | ✅ | |
| Generated column | ✅ | |
| Data lineage | ✅ | ✅ |
| Table comments | ✅ | ✅ |
| Foreign keys | ✅ | ✅ |
| Primary keys | ✅ | ✅ |
| Unique keys (indexes) | ✅ | ✅ |
| Triggers | ✅ | |
| When triggered | ✅ | |
| Script | ✅ |
Views
| Imported | Editable | |
|---|---|---|
| Views | ✅ | ✅ |
| Script | ✅ | ✅ |
| Columns | ✅ | ✅ |
| Data types | ✅ | |
| Nullability | ✅ | |
| Default value | ✅ | |
| Generated column | ✅ | |
| Data lineage | ✅ | ✅ |
Stored procedures
| Imported | Editable | |
|---|---|---|
| Stored procedures | ✅ | ✅ |
| Script | ✅ | ✅ |
| Parameters | ✅ (≥5.5) | ✅ |
| Data types | ✅ | |
| Mode | ✅ | |
| Data lineage | ✅ | ✅ |
SQL Queries (SELECTs in procedures)
If a procedure returns a result set with a SELECT statement, a SQL Query object will be created in the documentation to represent the output.
For example, if a procedure returns a table with multiple columns:
Dataedo will create a SQL Query object in the documentation.
This object is in a parent-child relationship with the procedure from which it is derived, and contains columns and script that are used in the lineage – read more about automatic lineage for MySQL.
| Imported | Editable | |
|---|---|---|
| SQL Queries | ✅ | ✅ |
| Script | ✅ | ✅ |
| Columns | ✅ | ✅ |
| Data types | ✅ |
User-defined Functions
| Imported | Editable | |
|---|---|---|
| User-defined Functions | ✅ | ✅ |
| Script | ✅ | ✅ |
| Parameters | ✅ (≥5.5) | ✅ |
| Return value | ✅ (≥5.5) | ✅ |
| Data types | ✅ | |
| Mode | ✅ |
* Column-level data lineage is retrieved using Dataedo SQL parser. Read more about the capabilities of MySQL SQL parser.
Comments
Dataedo reads MySQL comments from the following objects:
| Object | Read | Write back |
|---|---|---|
| Table comments | ✅ | |
| Column comments | ✅ | |
| Primary keys | ✅ | |
| Unique indexes | ✅ | |
| Procedures | ✅ | |
| Functions | ✅ |
Dataedo does not write comments back to MySQL.
Data profiling
Dataedo supports the following data profiling in MySQL:
| Profile | Support |
|---|---|
| Table row count | ✅ |
| Table sample data | ✅ |
| Column distribution (unique, non-unique, null, empty values) | ✅ |
| Min, max values | ✅ |
| Average | ✅ |
| Variance | ✅ |
| Standard deviation | ✅ |
| Min-max span | ✅ |
| Number of distinct values | ✅ |
| Top 10/100/1000 values | ✅ |
| Values if less than 1000 distinct | ✅ |
| 10 random values | ✅ |
Read more about profiling in the Data Profiling documentation.
Data Quality
Users will be able to check if data in MySQL tables is accurate, consistent, complete, and reliable using Data Quality functionality. Data Quality requires SELECT permission over the tested object.
Data Lineage
| Source | Method |
|---|---|
| Views - column level | From SQL parsing |
| Procedures - column level | From SQL parsing |
More details about MySQL lineage here
Data lineage is retrieved using the Dataedo SQL parser. Read more about the capabilities of the MySQL SQL parser.
Limitations
The following schema elements currently are not supported:
- Check constraints (vote)
- Non-unique indexes (vote)
- Dependencies - are not presented by MySQL
- SSL connection is supported only for MySQL 8.0.
- Parameters of procedures and functions are not available on MySQL 5.1.
Supported cloud databases
Dataedo should work with all cloud instances of MySQL database. We have tested it with the following services:
