Azure Table Storage to MySQL Integration

How Datrise loads Azure Table Storage into MySQL

Datrise syncs Azure Table Storage's tables, entities, partition keys, row keys, properties, and timestamps into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Azure Table Storage: Key-value NoSQL store on Azure.

MySQL: Widely used OSS relational engine (InnoDB).

How Azure Table Storage entities map to MySQL

Azure Table Storage entity	MySQL object	Notes
tables	`azure_table_storage_tables`	id PK · custom fields → JSON columns
entities	`azure_table_storage_entities`	id PK · linked to azure_table_storage_tables
partition keys	`azure_table_storage_partition_keys`	id PK · linked to azure_table_storage_tables
row keys	`azure_table_storage_row_keys`	id PK · linked to azure_table_storage_tables

FAQ

How does Datrise handle Azure Table Storage's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Azure Table Storage to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Azure Table Storage to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.