Real-time
Two-way sync
Changes in SQL Server or Treasuredata instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Analytics
SQL Server to Treasuredata integration — real-time, two-way sync
Keep SQL Server 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 SQL Server and Treasuredata
Give Treasuredata the users, events, and records that live in SQL Server in real time, and sync the cohorts and scores Treasuredata computes back into SQL Server where your applications read them.
A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Treasuredata is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from SQL Server into Treasuredata usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.
Stacksync syncs Schemas, Tables, Views, Columns in SQL Server with Segments, Journeys, Predictive Segments, Scheduled Queries in Treasuredata in real time and in both directions. Operational rows flow into Treasuredata as they change, so dashboards read current data with no pipeline to maintain, and the segments, cohorts, or scores Treasuredata computes flow back into SQL Server, where the applications and services that read from it get them at normal query latency. Field-level mapping, schema and type translation, and conflict resolution are handled for you.
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 Bi-directional sync between SQL Server rows and CRM objects so .NET line-of-business apps and sales tools share one dataset
- 04 Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
Common sync patterns
Filter and grouping dimensions kept fresh
Attributes teams slice by, such as plan, region, or account owner, stay current in Treasuredata because they sync from SQL Server as they change, instead of going stale after a one-time import.
Where Treasuredata tracks product events: behavior onto stored records
Signup, usage, and lifecycle events captured in Treasuredata sync into SQL Server as rows, so applications and internal tools can read behavioral data next to the records they already keep.
Where Treasuredata builds cohorts or scores: results your services can read
Segments, cohorts, or scores computed in Treasuredata sync back into SQL Server, where the services that read from the database act on them at query speed without calling the analytics API.
What you can sync between SQL Server 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.
| SQL Server objects | Treasuredata objects | How this pairing syncs | |
|---|---|---|---|
| Databases Instance-level databases that scope a sync's reads and writes. | Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables The primary sync target; rows map to records in connected systems. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. | Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. | CDC Change Tables is specific to SQL Server and Query Jobs to Treasuredata — each maps to any object or custom field on the other side. | |
| Stored Procedures T-SQL logic that can validate or post-process synced rows. | 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. | Stored Procedures is specific to SQL Server and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Schemas Namespaces (dbo and custom) used to organize synced tables. | 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 SQL Server and Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Views Read-side projections used as outbound sync sources. | Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. | Views is specific to SQL Server and Journeys to Treasuredata — each maps to any object or custom field on the other side. |
How changes propagate between SQL Server 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.
SQL Server Treasuredata 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 written to Treasuredata through its API, with automatic retries and rate-limit backoff.
Treasuredata SQL Server 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 SQL Server as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
- 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 SQL Server ⇄ Treasuredata
Connect SQL Server and Treasuredata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SQL Server–Treasuredata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever SQL Server 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 SQL Server or Treasuredata record.
Observability
Monitoring
Track your SQL Server ⇄ Treasuredata sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between SQL Server and Treasuredata.
How the SQL Server and Treasuredata connectors work
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
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 SQL Server 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.
- 01
Connect your apps
Authenticate SQL Server 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.
SQL Server
connected
Treasuredata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the SQL Server 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.
objects · SQL Server ⇄ TreasuredataCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
SQL Server TreasuredataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
SQL Server and Treasuredata integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between SQL Server and Treasuredata: authenticate both systems, choose the objects to sync (such as SQL Server's Databases and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for SQL Server and Treasuredata: Filter and grouping dimensions kept fresh; Where Treasuredata tracks product events: behavior onto stored records; Where Treasuredata builds cohorts or scores: results your services can read. Attributes teams slice by, such as plan, region, or account owner, stay current in Treasuredata because they sync from SQL Server as they change, instead of going stale after a one-time import.
-
SQL Server: 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. Treasuredata: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Treasuredata: TD storage (Plazma) is append/columnar-oriented — there is no native per-row change-data-capture stream, so incremental reads rely on polling a time or updated-at column. SQL Server: Native Change Data Capture reads inserts, updates, and deletes from the transaction log into change tables without touching application code. Stacksync's field mapping accounts for these differences between SQL Server and Treasuredata 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 SQL Server and Treasuredata records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed SQL Server and Treasuredata connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom SQL Server–Treasuredata integration in-house.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 413 integrations available for SQL Server and Treasuredata.
Popular · 4 of 413
No integrations match .
