DatriseAI-first ETL

Square Azure Synapse

AI-first ETL from Square into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Square into Azure Synapse

Datrise syncs Square's payments, orders, customers, catalog items, and locations 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

Square: Payments and commerce platform for retail and online sellers.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Square entities map to Azure Synapse

Square entityAzure Synapse objectNotes
paymentssquare_paymentsid PK · custom fields → NVARCHAR(MAX) JSON columns
orderssquare_ordersid PK · linked to square_payments
customerssquare_customersid PK · linked to square_payments
catalog itemssquare_catalog_itemsid PK · linked to square_payments

FAQ

How does Datrise handle Square'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 Square 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 Square 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.