Skip to main content
SQL Server · change data capture

Replicate SQL Server to your cloud warehouse.

Describe the sync in plain English, approve it once, and rsync.ai streams every change from SQL Server into Snowflake, BigQuery, Databricks, or Postgres — in real time.

Real-time CDCYou approve every syncNo per-row pricing
Connect SQL Server free →See how a sync runs
Log-based CDC, no polling You approve before anything moves
Destinations

Send SQL Server data where your team already works.

Pick where it lands. rsync.ai builds and runs the pipeline — you approve it before anything moves.

Cloud warehouse

Land typed, query-ready tables for BI and analytics — incremental after the first snapshot.

BigQueryDatabricksSnowflakeRedshift

Another database

Replicate SQL Server into Postgres or MySQL with automatic type mapping and real-time CDC.

PostgreSQLMySQL

Data lake / storage

Write Parquet, JSON, or CSV to object storage for your lake, byte-checked on every file.

Amazon S3GCSAzure Blob
What syncs

Every SQL Server object your pipeline needs.

Tables
Views
Schemas
Primary keys
CDC change streams
Snapshot + incremental
DATETIME2 → TIMESTAMP
UNIQUEIDENTIFIER → UUID
How it works

Four steps. You are in the loop for each one.

01

Describe it

Say what to replicate in plain English — no SQL, no connector config.

02

Review the plan

rsync.ai discovers the schema, maps types, and flags any PII before a row moves.

03

Approve

Nothing runs until you say yes. Later schema changes pause for the same review.

04

Stream

CDC keeps the destination live within seconds; a failed run resumes where it stopped.

Compare

Why teams move SQL Server this way.

What you care aboutSSIS / manualAWS DMSPer-row ETLrsync.ai
Set up without an engineerNoConsole formsRarelyPlain English
Real-time, log-based CDCBatchYesVariesYes
You approve before it runsn/aNoNoYes
Cost as volume growsYour timePer hour + I/ORises per rowPer GB, not per row
Run in your own VPCYesAWS onlyVariesComing soon

Straight about status: the SQL Server source and the BigQuery, Databricks, Postgres, MySQL, and storage destinations are live in production. Snowflake and Redshift are in preview. Self-hosting in your own VPC is coming soon — today rsync.ai runs as a managed cloud.

FAQ

SQL Server replication — common questions

How fresh is the data?
You choose the schedule, from a few times a day down to near real time. rsync.ai reads SQL Server's change log (CDC), so it writes only the rows that changed — and a failed run resumes where it stopped instead of starting over.
Do I need to write SQL or configure a connector?
No. Describe the sync in plain English. rsync.ai discovers the schema, maps SQL Server types to the destination, flags PII, and shows you the plan. Nothing runs until you approve it.
Which SQL Server types are handled?
Common types map automatically — DATETIME2, UNIQUEIDENTIFIER, DECIMAL, NVARCHAR, BIT, and more — with the exact mapping shown in the review step before the first row moves, so there are no silent conversions.
How are you priced?
On data volume (GB moved), not per row or Monthly Active Rows — so your bill tracks bytes moved, not row counts. Each plan includes a GB allowance, and pipelines pause at the limit rather than silently running up charges; beyond the allowance it's a flat $3/GB.
Who controls what moves?
You do. Every sync waits for your approval, PII is flagged before it lands, and later schema changes pause for review. Self-hosting entirely in your own VPC is coming soon for teams that need data to never leave their network.

Put your SQL Server data in the warehouse.

Connect your database free and send your first live sync to BigQuery or Databricks today.

Connect SQL Server free →See how it works
Live on rsync.ai Cloud today · self-hosting coming soon