DatriseAI-first ETL

News API to Azure Synapse Integration

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

How Datrise loads News API into Azure Synapse

Datrise syncs News API's articles, sources, headlines, publication dates, categories, and search queries 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

News API: Aggregated news headlines across publishers.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How News API entities map to Azure Synapse

News API entityAzure Synapse objectNotes
articlesnews_api_articlesid PK · custom fields → NVARCHAR(MAX) JSON columns
sourcesnews_api_sourcesid PK · linked to news_api_articles
headlinesnews_api_headlinesid PK · linked to news_api_articles
publication datesnews_api_publication_datesid PK · linked to news_api_articles

FAQ

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