MySQL
| Type of Support: | Read & Write, In-Database |
| Validated On: | Database version 5.1 Database version 5.6, 5.7 (Spatial support) ODBC client version 5.01.04.00, 5.01.12.00 ODBC client version 5.02.06.00, ANSI and Unicode® encoding (Spatial support) |
| Connection Type: | ODBC (32- and 64-bit) |
| Driver Details: |
The ODBC driver can be downloaded from MySQL. In-Database processing requires 64-bit database drivers. |
Alteryx tools used to connect
- Input Data Tool and Output Data Tool (For standard workflow processing)
- In-Database tools Connect In-DB Tool and Data Stream In Tool (For In-Database workflow processing).
Additional Details
Limitations
Database Version 5.1
- Maximum Columns In Table: 4096
- Maximum Column Name Length: 64 characters
- Maximum Row Size: 65535 bytes (does not include LOB size)
ODBC Version 5.01.04.00 (32- and 64-bit)
- Fixed Numeric is transported as a SQL_C_CHAR; SQL_NUMERIC not supported.
- Known bug with BIT datatypes (MySQL Bug#37118) - returns false no matter what you do.
OLEDB
- MySQL does not have a native OLEDB provider.
Spatial
- Projections are not supported for writing spatial data.
- The Spatial Match Tool only supports the "Intersects" calculation type.
- The Find Nearest Tool is not supported.