Skip to content
Data warehouse ⇄ Database

Exasol to SQL Server integration — real-time, two-way sync

Keep Exasol and SQL Server 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 Exasol and SQL Server

Connect SQL Server and Exasol with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want SQL Server's rows in Exasol, 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 SQL Server where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in SQL Server sync into Exasol in real time, and result tables in Exasol sync back into SQL Server, with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Sync computed metrics or customer segments from Exasol back into a CRM for sales and marketing use (reverse ETL).
  • 02 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
  • 03 Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
  • 04 Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems

Common sync patterns

Offload heavy reads

Point analytical queries at the synced copy in Exasol and keep SQL Server focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from SQL Server land in Exasol as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Exasol sync into SQL Server, where whatever reads from that database gets them without querying the warehouse.

What you can sync between Exasol and SQL Server

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.

Exasol objects SQL Server objects How this pairing syncs
Schemas Namespaces that group the tables a sync reads from or writes into. Schemas Namespaces (dbo and custom) used to organize synced tables. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Tables Primary sync target; columnar relational tables written with standard SQL. Tables The primary sync target; rows map to records in connected systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Read-only query surfaces often used as curated sources for reverse ETL. Views Read-side projections used as outbound sync sources. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
UDF scripts In-database functions that can transform synced data after load. Stored Procedures T-SQL logic that can validate or post-process synced rows. UDF scripts is specific to Exasol and Stored Procedures to SQL Server — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. Databases Instance-level databases that scope a sync's reads and writes. Users and roles is specific to Exasol and Databases to SQL Server — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Columns Field-level mapping targets with T-SQL types. Virtual schemas is specific to Exasol and Columns to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Exasol and SQL Server

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.

Exasol SQL Server Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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

SQL Server Exasol Sub-second propagation

DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).

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

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Exasol ⇄ SQL Server

Connect Exasol and SQL Server for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–SQL Server connection.

Real-time

Two-way sync

Changes in Exasol or SQL Server instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Exasol or SQL Server 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 Exasol or SQL Server record.

Observability

Monitoring

Track your Exasol ⇄ SQL Server sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Exasol and SQL Server.

How the Exasol and SQL Server connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

How to connect Exasol to SQL Server — 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 Exasol and SQL Server 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
    Exasol connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Exasol and SQL Server 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 · Exasol ⇄ SQL Server
    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
    Exasol SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Exasol and SQL Server 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 465 integrations available for Exasol and SQL Server.

Popular · 5 of 465
All Exasol integrations All SQL Server 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