SQL Server to PostgreSQL: Migration Challenges & Solutions
summary
Migrating from SQL Server to PostgreSQL hits specific pain points: schema and T‑SQL incompatibilities, backups, collation and case sensitivity, and MVCC maintenance. Practical answers: use pg_dump for logical exports and pg_basebackup (Postgres 17 adds incremental) plus WAL archiving for PITR; use Babelfish to reduce T‑SQL rewrite; use CI text/ICU collations or lowercase identifiers for case handling; use pgloader or COPY for bulk loads, foreign data wrapper and logical decoding for CDC, and tune autovacuum, temp buffers and tablespaces. Teams report talking to ~100 DBAs and find these tools largely effective.
AI-written summary · about
chapters (13)
- 0:00Introduction and motivation
- 3:25Architectural comparisons
- 7:24Read and write operations
- 10:01Recovery and log models
- 11:44Memory architecture
- 14:16Temporary object management
- 16:42Concurrency and isolation
- 19:47Developer and data features
- 28:18Collation and case sensitivity
- 31:50Authentication and federation
- 34:40Access methods and syntax
- 36:24Administrative tasks
- 38:58Migration and tooling
related talks
27mMigrating from MSSQL to PostgreSQL
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
46mPostgres for the SQL Server DBA
06mMigration Consideration Oracle to PostgreSQL
46mThe Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL
29mTales from the Field - Oracle to PostgreSQL migrations
38mSwitching Teams: Moving an Application from MySQL to PostgreSQL
36mTales from the Postgres Front, and What We Can Learn
