WaiterAid to Azure Synapse Integration

How Datrise loads WaiterAid into Azure Synapse

Datrise syncs WaiterAid's bookings, guests, tables, restaurants, time slots, and booking statuses into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

WaiterAid: Restaurant reservations and table management.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How WaiterAid entities map to Azure Synapse

WaiterAid entity	Azure Synapse object	Notes
bookings	`waiteraid_bookings`	id PK · custom fields → NVARCHAR(MAX) JSON columns
guests	`waiteraid_guests`	id PK · linked to waiteraid_bookings
tables	`waiteraid_tables`	id PK · linked to waiteraid_bookings
restaurants	`waiteraid_restaurants`	id PK · linked to waiteraid_bookings

FAQ

How does Datrise handle WaiterAid's custom fields in Azure Synapse?

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

How does the WaiterAid to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect WaiterAid to Azure Synapse 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.