Azure Blob Storage to MySQL Integration

How Datrise loads Azure Blob Storage into MySQL

Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions 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 Blob Storage: Object storage for blobs and data lake files on Azure.

MySQL: Widely used OSS relational engine (InnoDB).

How Azure Blob Storage entities map to MySQL

Azure Blob Storage entity	MySQL object	Notes
containers	`azureblobstorage_containers`	id PK · custom fields → JSON columns
blobs	`azureblobstorage_blobs`	id PK · linked to azureblobstorage_containers
blob metadata	`azureblobstorage_blob_metadata`	id PK · linked to azureblobstorage_containers
snapshots	`azureblobstorage_snapshots`	id PK · linked to azureblobstorage_containers

FAQ

How does Datrise handle Azure Blob 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 Blob 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 Blob 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.