DatriseAI-first ETL

Appfollow to Azure Synapse Integration

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

How Datrise loads Appfollow into Azure Synapse

Datrise syncs Appfollow's reviews, ratings, app rankings, keywords, replies, and store listings 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

Appfollow: App store review and rankings monitoring.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Appfollow entities map to Azure Synapse

Appfollow entityAzure Synapse objectNotes
reviewsappfollow_reviewsid PK · custom fields → NVARCHAR(MAX) JSON columns
ratingsappfollow_ratingsid PK · linked to appfollow_reviews
app rankingsappfollow_app_rankingsid PK · linked to appfollow_reviews
keywordsappfollow_keywordsid PK · linked to appfollow_reviews

FAQ

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