Azure Blob Storage to Chartio Integration

How Datrise loads Azure Blob Storage into Chartio

Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions into Chartio as SQL tables a visual-SQL explorer connects to. Flexible or custom fields land in flattened columns for visual SQL, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Visual-SQL tools build joins from your schema, so Datrise lands clearly related tables with stable id columns.

Ideal for drag-and-drop charting over a database.

Endpoints

Azure Blob Storage: Object storage for blobs and data lake files on Azure.

Chartio: Cloud BI for exploring warehouse data with drag-and-drop charts.

How Azure Blob Storage entities map to Chartio

Azure Blob Storage entity	Chartio object	Notes
containers	`azureblobstorage_containers`	id PK · custom fields → flattened columns for visual SQL
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 Chartio?

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

How does the Azure Blob Storage to Chartio sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Azure Blob Storage to Chartio 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.