SQL Server Connector

Extract from Microsoft SQL Server (2016+) or Azure SQL Database with Standard or Change Tracking mode, or load data into SQL Server as a destination.

SourceDestinationSilver

Start for Free Source Documentation Destination Documentation

Evaluating against Fivetran? See how Supaflow handles SQL Server pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Load SQL Server into Snowflake

Dedicated pages for destination-specific setup, buyer questions, and Snowflake sync behavior.

SQL Server to Snowflake

Replicate SQL Server tables into Snowflake with Change Tracking and hard-delete capture.

View pipeline page

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Standard and Change Tracking Sync Modes

Standard mode uses a cursor column to detect new and changed rows. Change Tracking mode uses SQL Server built-in Change Tracking to capture inserts, updates, and deletes with destination delete markers.

Username/Password Authentication with Encryption

Connects with SQL Server credentials. Encryption is configurable: true (default, recommended for Azure SQL), false, or strict (TDS 8.0). Supports Trust Server Certificate for self-signed certificates.

Resumable Large-Table Loads

Large tables load in bounded, resumable batches, so an interrupted initial sync picks up where it left off instead of restarting. Batch size is tunable, with an optional memory-aware mode for very wide rows.

Azure SQL Database Support

Works with Azure SQL Database using contained database users. Add the Supaflow IP (18.214.240.61) to Azure Networking > Firewall rules.

Supported Objects

Database Objects

Tables

All tables the connecting user has SELECT permission on.

Schemas

All schemas the user has access to (e.g., dbo, custom schemas).

Change Tracking (when enabled)

Tracked tables

Tables with SQL Server Change Tracking enabled and a primary key.

Delete markers

Deleted rows can be marked in the destination for downstream handling.

How It Works

Prepare SQL Server access

Create a dedicated read-only login and user with SELECT privileges on target schemas or tables. For Azure SQL, create a contained database user. Add Supaflow IP 18.214.240.61 to your firewall or Azure Networking > Firewall rules.

Enable Change Tracking (optional)

If using Change Tracking mode, enable it on the database and each synced table with at least 7-day retention. Every synced table must have a primary key, and the Supaflow user needs permission to view change tracking.

Enter connection details

Provide the hostname (e.g., myserver.database.windows.net for Azure), port (default 1433), database name, username, and password. Select Standard or Change Tracking mode and encryption settings.

Test and save

Click Test & Save to verify the connection. Supaflow discovers all accessible tables. In Change Tracking mode, tables without Change Tracking enabled are skipped during discovery.

Use Cases

SQL Server to Snowflake replication

Replicate SQL Server tables into Snowflake with cursor-based or Change Tracking incremental sync for near-real-time analytics.

Azure SQL Database offloading

Move reporting workloads off Azure SQL by syncing data into a warehouse, reducing DTU consumption on your production database.

Delete detection with Change Tracking

Use Change Tracking mode to capture hard deletes in SQL Server. Deleted rows are marked in the destination, enabling soft-delete patterns in your warehouse.

Reverse ETL back to SQL Server

Write enriched or aggregated data from your warehouse back into SQL Server or Azure SQL Database for use by operational applications and reporting.

Frequently Asked Questions

How do I connect Supaflow to an on-premises SQL Server?

For production, deploy a self-hosted Docker Agent on a stable host inside the same private network as SQL Server. The agent connects to SQL Server over the private network and polls Supaflow over outbound HTTPS, so the database port stays private. For a quick proof-of-concept connectivity test, you can use a temporary ngrok or bore TCP tunnel; do not use a temporary public tunnel for production or sensitive data.

Deploy a self-hosted Docker Agent Test connectivity with ngrok or bore

Which SQL Server versions are supported?

SQL Server 2016 or higher, and Azure SQL Database. Change Tracking is available in all supported versions.

Can I use SQL Server as a destination?

Yes. Supaflow can load data from any supported source into Microsoft SQL Server or Azure SQL Database. Target schemas and tables are created automatically, using the same username/password authentication and encryption options as a SQL Server source connection.

What is the difference between Standard and Change Tracking modes?

Standard mode uses a cursor column (timestamp) to detect inserts and updates but cannot detect deletes. Change Tracking mode uses SQL Server built-in change tracking to capture all changes including deletes.

Do I need to whitelist an IP address?

If your SQL Server restricts inbound connections, add 18.214.240.61 to your firewall rules. For Azure SQL, this is mandatory -- add the IP in Azure portal > SQL server > Networking > Firewall rules.

What happens to tables without Change Tracking enabled?

Tables without Change Tracking enabled are automatically skipped during schema discovery in Change Tracking mode. Enable Change Tracking on each table you want to sync.