DatriseAI-first ETL

Newsdata to Azure Synapse Integration

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

How Datrise loads Newsdata into Azure Synapse

Datrise syncs Newsdata's articles, sources, categories, countries, publication dates, and keywords 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

Newsdata: News feed API with topic and country filters.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Newsdata entities map to Azure Synapse

Newsdata entityAzure Synapse objectNotes
articlesnewsdata_articlesid PK · custom fields → NVARCHAR(MAX) JSON columns
sourcesnewsdata_sourcesid PK · linked to newsdata_articles
categoriesnewsdata_categoriesid PK · linked to newsdata_articles
countriesnewsdata_countriesid PK · linked to newsdata_articles

FAQ

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