Skip to content
Database · Two-way sync platform

SQL Server connector for two-way sync.

Keep SQL Server and your business systems aligned with Stacksync. Sync Tables within the connector’s object and field requirements, with two-way sync for eligible records.

  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to SQL Server

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
Record types

SQL Server objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Tables
Check object and field eligibility in the setup guide.

Read the SQL Server object and setup guide

Connection setup

SQL Server connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Account access
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
How changes are detected
Native SQL Server CDC captures changes after an administrator enables CDC and creates the Stacksync wrapper procedures.

Sync directions

  • Read data Documented
  • Write data Documented
SQL ServerStacksync setup guide
Setup prerequisites for your administrator
  • Use a single generated primary key per table and grant the Stacksync user the required table access.
  • Have a DBA run the one-time CDC setup script and grant execution on its wrapper procedures. Verify SQL Server Agent where the deployment requires it.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your SQL Server integration.

Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
SQL ServerSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Keep the database-generated local primary key separate from the external application record ID. Add a unique matching rule for the external ID, and test repeated delivery without creating a second business record.
Load related records in the right order
Resolve foreign-key dependencies and confirm the CDC wrapper procedures and required execution grants. Track schema/table/column renames as configuration changes.

Mapping checks by record type

Tables

Check the object requirements below

Identity
Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema.
Fields to consider
Local record key · External application ID · Required business fields · Parent record references
Related records to resolve first
Resolve foreign-key dependencies and confirm the CDC wrapper procedures and required execution grants. Track schema/table/column renames as configuration changes.
Test before going live
Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the SQL Server integration in four steps.

Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure.

View the four setup tests and expected results

  1. Verify SQL Server connectivity and database privileges

    Use the documented setup from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture.

    Expected result: The approved role can access the selected data and capture later changes without depending on an administrator’s personal session.

  2. Verify capture after the one-time CDC setup

    Have the DBA enable the documented CDC setup, then insert and update a test row. Check SQL Server Agent where the deployment requires it.

    Expected result: The approved user can execute the wrapper procedures and a later row change reaches its permitted destination.

  3. Test writes in the directions you need

    Select one eligible SQL Server object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected SQL Server records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your SQL Server integration.

Diagnose record matching, delayed changes, and rejected operations
The initial table copy succeeds but updates stop
Check CDC enablement, wrapper-procedure execution grants, and the deployment’s SQL Server Agent requirement before changing field mappings.
The first load looks correct but later results differ
Native SQL Server CDC captures changes after an administrator enables CDC and creates the Stacksync wrapper procedures. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific SQL Server object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your SQL Server workflow with an engineer

SQL Server integration guides

FAQ

SQL Server connector FAQ

How should I plan an integration with SQL Server?

Generated primary keys and administrator-provisioned CDC are prerequisites for each selected table. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the SQL Server connector write changes back?

Stacksync supports reads and writes for eligible SQL Server objects. Check the selected fields, account permissions, and the other system’s connector. Have the DBA enable the documented CDC setup, then insert and update a test row. Check SQL Server Agent where the deployment requires it.

Which identifiers should I preserve for SQL Server data?

Keep the database-generated local primary key separate from the external application record ID. Add a unique matching rule for the external ID, and test repeated delivery without creating a second business record.

Which related records should I load first for SQL Server?

Resolve foreign-key dependencies and confirm the CDC wrapper procedures and required execution grants. Track schema/table/column renames as configuration changes.

What should I check if SQL Server data is missing or delayed?

Check CDC enablement, wrapper-procedure execution grants, and the deployment’s SQL Server Agent requirement before changing field mappings.

What will we cover in a SQL Server integration demo?

Start with one workflow and a sample record from Tables. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Explore SQL Server connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

287 integration guides

CRM · 45

ERP · 39

Database · 49

Data warehouse · 29

Business productivity · 39

Accounting and finance · 17

AI · 5

Analytics · 7

Communications · 5

Developer tools · 11

E-commerce · 8

Human resources · 14

Marketing · 9

Security and identity · 6

Storage · 4

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 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started