Query federation for MySQL in Databricks SQL without Unity Catalog (Experimental)

Experimental

The configurations described in this article are Experimental. Experimental features are provided as-is and are not supported by Databricks through customer technical support. To get full query federation support, you should instead use Lakehouse Federation, which enables your Databricks users to take advantage of Unity Catalog syntax and data governance tools.

This article describes how to configure read-only query federation to MySQL on serverless and pro SQL warehouses.

You configure connections to MySQL at the table level. You can use secrets to store and access text credentials without displaying them in plaintext. See the following example:

DROP TABLE IF EXISTS mysql_table;
CREATE TABLE mysql_table
USING mysql
OPTIONS (
  dbtable '<table-name>',
  host '<database-host-url>',
  port '3306',
  database '<database-name>',
  user secret('mysql_creds', 'my_username'),
  password secret('mysql_creds', 'my_password')
);