Two-way sync
Changes in Azure Synapse Analytics or Reltio instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics and Reltio in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Reltio's rows in Azure Synapse Analytics, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Reltio where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Reltio sync into Azure Synapse Analytics in real time, and result tables in Azure Synapse Analytics sync back into Reltio, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Azure Synapse Analytics and keep Reltio focused on its operational workload.
Rows from Reltio land in Azure Synapse Analytics as they change, replacing hand-built CDC and batch extract jobs.
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 | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | SQL pools is specific to Azure Synapse Analytics and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Crosswalks to Reltio — 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. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | External tables is specific to Azure Synapse Analytics and Interactions to Reltio — 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. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Views is specific to Azure Synapse Analytics and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Schemas is specific to Azure Synapse Analytics and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Materialized views is specific to Azure Synapse Analytics and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. |
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.
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 Reltio through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Reltio connection.
Changes in Azure Synapse Analytics or Reltio instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Reltio data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Reltio record.
Track your Azure Synapse Analytics ⇄ Reltio sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Reltio.
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.
Authenticate Azure Synapse Analytics and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Azure Synapse Analytics and Reltio 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure Synapse Analytics and Reltio: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's SQL pools and Tables (dedicated SQL pool)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Azure Synapse Analytics and Reltio: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Azure Synapse Analytics: 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. Reltio: Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}. Authentication: OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api). Stacksync manages authentication, retries, and rate limits on both sides.
Azure Synapse Analytics: Batch-style loading (staged, set-based inserts) performs far better than row-by-row writes, which shapes how a sync should deliver data into it. Reltio: Reltio has no database-style CDC log external tools consume; incremental sync filters entities and relations on updateTime (epoch-ms). Reltio separately can publish change events to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka) — a queue feed, not HTTP webhooks. Stacksync's field mapping accounts for these differences between Azure Synapse Analytics and Reltio without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Synapse Analytics and Reltio records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Synapse Analytics and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Synapse Analytics–Reltio integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 466 integrations available for Azure Synapse Analytics and Reltio.