Little Green Light to Azure Synapse Integration

How Datrise loads Little Green Light into Azure Synapse

Datrise syncs Little Green Light's constituents, gifts, pledges, campaigns, events, and volunteer records 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

Little Green Light: Fundraising CRM for small nonprofit development teams.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Little Green Light entities map to Azure Synapse

Little Green Light entity	Azure Synapse object	Notes
constituents	`little_green_light_constituents`	id PK · custom fields → NVARCHAR(MAX) JSON columns
gifts	`little_green_light_gifts`	id PK · linked to little_green_light_constituents
pledges	`little_green_light_pledges`	id PK · linked to little_green_light_constituents
campaigns	`little_green_light_campaigns`	id PK · linked to little_green_light_constituents

FAQ

How does Datrise handle Little Green Light'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 Little Green Light 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 Little Green Light 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.