SQL Server to Snowflake migration and replication, one connector

Convert the schema to Snowflake types, backfill each table once from a replica, keep the two in step with incremental loads, then move the reports and retire the old feed. Each pass is reversible on its own, so you never need a big-bang weekend cutover.

Integers become NUMBER(38,0), NVARCHAR becomes VARCHAR, and BIT becomes BOOLEAN. The three to decide deliberately are MONEY, which must become NUMBER(19,4) and never FLOAT, DATETIME2, which belongs in TIMESTAMP_NTZ, and DATETIMEOFFSET, the only type that should become TIMESTAMP_TZ.

Enable SQL Server change data capture, which reads the transaction log and writes inserts, updates, and deletes into change tables. CDC runs as two SQL Server Agent jobs, so the Agent service has to be running. It is the only method that also gives you deletes.

For analytics and reporting, yes. For transactional workloads, no. Snowflake has no equivalent of the single-row seeks, enforced foreign keys, and low-latency writes an application needs. Most teams run both: SQL Server keeps the application, Snowflake owns the reporting.

Usually identifier case. Snowflake folds unquoted identifiers to uppercase, so a column created as OrderID is physically ORDERID and a query selecting the quoted "OrderID" fails. Create everything unquoted and reference it unquoted rather than quoting mixed case forever.

The SQL Server to Snowflake connector from Adapters replicates SQL Server tables into Snowflake on an incremental schedule, converting T-SQL data types to their Snowflake equivalents and merging on the primary key so reporting reads the warehouse instead of your transactional database. Field mapping takes about a minute and no code is required.

Yes. This SQL Server to Snowflake connector ships prebuilt: the field mapping is wired the moment you pick the pair, transforms are included, and the first sync can run within minutes. No code or engineering sprint required.

Pricing is flat and monthly: Starter at $49, Growth at $149, Scale at $399. Every plan includes this pair, visual field mapping, and per-record logs. There are no per-task or per-row fees, so the bill stays the same as volume grows.

Hourly on Starter, every 5 minutes on Growth, and down to every minute on Scale. Failed records retry automatically with backoff, and alerting plus a full per-record log come standard on every run.

No. Fields are auto-mapped the moment you pick the pair, and you can rewire any mapping visually before the first sync. Incremental runs use a SQL Server ModifiedDate watermark, or the CDC change tables when you need deletes, so only changed rows load; MONEY and SMALLMONEY become NUMBER at full scale instead of a float that rounds cents, DECIMAL and NUMERIC keep their declared precision inside the Snowflake NUMBER limit of 38 digits, DATETIME and DATETIME2 land as TIMESTAMP_NTZ while DATETIMEOFFSET keeps its offset in TIMESTAMP_TZ, BIT becomes BOOLEAN, UNIQUEIDENTIFIER and XML land as VARCHAR, VARBINARY becomes BINARY, and every load MERGEs on the primary key so a replayed batch never duplicates a row.