source-sqlserver-ct: New connector docs and updated "when to use" #2624
+248
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
willdonnelly
changed the title
|
aeluce
reviewed
Jan 20, 2026
| We recommend using our [SQL Server CDC Connector](http://go.estuary.dev/source-sqlserver) | ||
| instead when possible. CDC provides lower latency data capture, delete and | ||
| update events, and typically has a smaller impact on the source database. | ||
| Estuary offers three SQL Server capture connectors. All work across self-hosted |
Collaborator
There was a problem hiding this comment.
We may want to phrase this as "three main SQL Server capture connectors and their variants" since someone searching the dashboard will find Azure, Amazon RDS, etc for SQL Server as well.
Relatedly, hopefully we're planning on updating the connector names to make it clear in the dashboard which options are CDC vs. CT.
|
|
||
| Follow the [Self-hosted SQL Server](#self-hosted-sql-server) setup instructions above, with the following Azure-specific notes: | ||
|
|
||
| - **Firewall rules**: Configure [server-level IP firewall rules](https://learn.microsoft.com/en-us/azure/azure-sql/database/firewall-configure?view=azuresql#use-the-azure-portal-to-manage-server-level-ip-firewall-rules) to allow the [Estuary Flow IP addresses](/reference/allow-ip-addresses), or set up an SSH tunnel as described in the self-hosted instructions. |
Collaborator
There was a problem hiding this comment.
Note that we're standardizing Estuary Flow to Estuary (#2562).
| configured when enabling Change Tracking. If the connector is offline for | ||
| longer than this retention period, or if it falls too far behind, it will | ||
| automatically perform a full backfill of impacted tables to re-establish | ||
| consistency. |
Collaborator
There was a problem hiding this comment.
Do we have a recommended minimum change tracking retention time?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Just a quick edit of the source-sqlserver docs for source-sqlserver-ct, and updated "when to use this connector" sections for all three connectors.
Part of estuary/connectors#3470