Skip to content
Data warehouse ⇄ Analytics

Azure Synapse Analytics to Treasuredata integration — real-time, two-way sync

Keep Azure Synapse Analytics and Treasuredata in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure Synapse Analytics and Treasuredata

Put the same events, users, and metrics on both sides: Treasuredata and Azure Synapse Analytics stay current in real time, in both directions.

Treasuredata is where teams explore, visualize, and report; Azure Synapse Analytics is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Stacksync syncs Segments, Journeys, Predictive Segments, Scheduled Queries in Treasuredata with Tables (dedicated SQL pool), External tables, Views, Schemas in Azure Synapse Analytics field by field, in real time, and in both directions. You decide which system owns which fields, and Stacksync resolves conflicts by rules you set. Whether the flow is warehouse tables feeding live reports or captured events and segments landing back in Azure Synapse Analytics, every copy stays consistent.

Common use cases

  • 01 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
  • 02 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
  • 03 Load CRM and ERP records into Synapse dedicated SQL pool tables for enterprise reporting.
  • 04 Publish warehouse aggregates (account health scores, LTV) from Synapse back into operational tools like a CRM.

Common sync patterns

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Treasuredata matches the Azure Synapse Analytics table it was built from instead of drifting between refreshes.

Where Azure Synapse Analytics holds the source tables: live data in the reporting layer

Records maintained in Azure Synapse Analytics flow into Treasuredata as they change, so dashboards and reports read current rows rather than an overnight extract.

What you can sync between Azure Synapse Analytics and Treasuredata

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Azure Synapse Analytics objects Treasuredata objects How this pairing syncs
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Databases to Treasuredata — each maps to any object or custom field on the other side.
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. External tables is specific to Azure Synapse Analytics and Tables to Treasuredata — each maps to any object or custom field on the other side.
Views Curated projections used when downstream tools should not read base tables directly. Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. Views is specific to Azure Synapse Analytics and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side.
Schemas Namespaces that separate staging, integration, and presentation layers. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. Schemas is specific to Azure Synapse Analytics and Segments to Treasuredata — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. Materialized views is specific to Azure Synapse Analytics and Journeys to Treasuredata — each maps to any object or custom field on the other side.
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. SQL pools is specific to Azure Synapse Analytics and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics and Treasuredata

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Azure Synapse Analytics Treasuredata Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.

Treasuredata Azure Synapse Analytics Interval-based propagation

DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.

DeliveryEach detected change is applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Azure Synapse Analytics ⇄ Treasuredata

Connect Azure Synapse Analytics and Treasuredata for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Treasuredata connection.

Real-time

Two-way sync

Changes in Azure Synapse Analytics or Treasuredata instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Synapse Analytics or Treasuredata data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure Synapse Analytics or Treasuredata record.

Observability

Monitoring

Track your Azure Synapse Analytics ⇄ Treasuredata sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Treasuredata.

How the Azure Synapse Analytics and Treasuredata connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

Treasuredata

Integration surface
TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
Authentication
API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
Change detection
Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
Capabilities
read · write
Rate limits
TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works

How to connect Azure Synapse Analytics to Treasuredata — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Azure Synapse Analytics and Treasuredata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Synapse Analytics connected
    Treasuredata connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Synapse Analytics and Treasuredata objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Synapse Analytics ⇄ Treasuredata
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Synapse Analytics Treasuredata
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Synapse Analytics and Treasuredata integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 415 integrations available for Azure Synapse Analytics and Treasuredata.

Popular · 5 of 415
All Azure Synapse Analytics integrations All Treasuredata integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own