SQL Server Connector
Extract data from Microsoft SQL Server (2016+) or Azure SQL Database. Supports Standard mode with cursor-based incremental sync and Change Tracking mode for full change capture including deletes.
Why Supaflow
All connectors included
No per-connector fees. Every connector is available on every plan.
Pay for compute, not rows
Credit-based pricing. No per-row charges, no MAR surprises.
One platform
Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.
Capabilities
Standard and Change Tracking Query Modes
Standard mode uses a cursor column (e.g., LastModifiedDate) to detect new and changed rows. Change Tracking mode uses SQL Server built-in Change Tracking to capture inserts, updates, and deletes with synthetic __ct_version and __ct_is_deleted columns.
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.
Keyset-Based Chunked Reads
Large tables are read in configurable chunks (default 1,000,000 rows) using primary key-based keyset pagination. Each chunk is resumable on failure. Memory-aware limiting dynamically reduces chunk size for 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.
Views
Standard views accessible to the connecting user.
Schemas
All schemas the user has access to (e.g., dbo, custom schemas).
Change Tracking (when enabled)
__ct_version
Synthetic column: Change Tracking version when the row was captured.
__ct_is_deleted
Synthetic column: 0 for active rows, 1 for deleted rows.
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 with at least 7-day retention (ALTER DATABASE SET CHANGE_TRACKING = ON) and on each table (ALTER TABLE ENABLE CHANGE_TRACKING). Every synced table must have a primary key. Grant VIEW CHANGE TRACKING to the Supaflow user.
Enter connection details
Provide the hostname (e.g., myserver.database.windows.net for Azure), port (default 1433), database name, username, and password. Select the query mode (STANDARD or CHANGE_TRACKING) and encryption settings.
Test and save
Click Test & Save to verify the connection. Supaflow discovers all accessible tables and views. In Change Tracking mode, tables without Change Tracking enabled are skipped with reason CHANGE_TRACKING_NOT_ENABLED.
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 appear in the destination with __ct_is_deleted = 1, enabling soft-delete patterns in your warehouse.
Frequently Asked Questions
Which SQL Server versions are supported?
What is the difference between Standard and Change Tracking modes?
Do I need to whitelist an IP address?
What happens to tables without Change Tracking in CT mode?
Need a connector we don't support yet?
Build one with AI-powered Connector Dev Skills.
Learn More About the Connector SDK
