Migrate SQL Server databases to Babelfish for Aurora PostgreSQL using change tracking with a linked server
Database Blog
This article discusses migrating SQL Server databases to Babelfish for Aurora PostgreSQL using change tracking with a linked server. It provides a workaround for situations where the SQL Server edition doesn't support transactional replication or change data capture.
Specifically, the article covers:
- Solution overview and architecture
- Prerequisites for testing the solution
- Enabling change tracking on the source SQL Server
- Migrating the source database with initial full load using AWS DMS
- Creating a linked server at the target Babelfish instance
- Creating an anchor table to store change tracking versions
- Extracting changed data from the source and loading it to the target
- Cleanup steps to remove resources
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jun 28
2024
2024
Workaround for T-SQL global temporary tables in Babelfish for Aurora PostgreSQL
Oct 1
2026
2026
Babelfish for Aurora PostgreSQL performance tuning
Jun 4
2024
2024
AWS DMS now supports Babelfish for Aurora PostgreSQL as a source
Jul 30
2026
2026
Modernize SQL Server databases to Aurora PostgreSQL using AWS Transform
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.