This version of Microsoft SQL Server reached end of life on February 15, 2020 and is no longer functioning.
Upgrade to the latest version (v1) to continue replicating data.
Microsoft SQL Server feature snapshot
A high-level look at Stitch's Microsoft SQL Server (v06-01-2016) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release status |
Sunset on February 15, 2020 |
Supported by | |
Stitch plan |
Standard |
Supported versions |
2000 - 2016 |
API availability |
Not available |
Singer GitHub repository |
Not applicable |
CONNECTION METHODS | |||
SSH connections |
Supported |
SSL connections |
Supported |
REPLICATION SETTINGS | |||
Anchor Scheduling |
Unsupported |
Advanced Scheduling |
Unsupported |
Table-level reset |
Supported |
Configurable Replication Methods |
Supported |
REPLICATION METHODS | |||
Log-based Replication |
Unsupported |
Key-based Replication |
Supported |
Full Table Replication |
Supported |
||
DATA SELECTION | |||
Table selection |
Supported |
Column selection |
Supported |
View replication |
Supported |
Select all |
Supported |
TRANSPARENCY | |||
Extraction Logs |
Unsupported |
Loading Reports |
Supported |
Troubleshooting
Connection issues and collation
If you’re experiencing connection issues and have verified that the database user has the correct permissions, check your server’s collation setting.
Connecting MSSQL to Stitch successfully requires that your server use case-insensitive collation.
Data discrepancies and database user language settings
If you’re missing data, check that the database user’s language setting is set to us_english
. Using a different setting can cause problems with replication, including issues with properly identifying new and updated data.
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.