DatriseAI-first ETL

NetSuite Azure Synapse

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

How Datrise loads NetSuite into Azure Synapse

Datrise syncs NetSuite's transactions, customers, items, subsidiaries, and GL activity 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

NetSuite: Cloud ERP for finance, inventory, and operations.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How NetSuite entities map to Azure Synapse

NetSuite entityAzure Synapse objectNotes
transactionsnetsuite_transactionsid PK · custom fields → NVARCHAR(MAX) JSON columns
customersnetsuite_customersid PK · linked to netsuite_transactions
itemsnetsuite_itemsid PK · linked to netsuite_transactions
subsidiariesnetsuite_subsidiariesid PK · linked to netsuite_transactions

FAQ

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