Migrating from MSSQL to PostgreSQL
summary
Real migration steps: compile and install the tds_fdw foreign data wrapper on a Linux/Postgres 9.6+ build, create foreign tables for the SQL Server information_schema and data, then copy ~several hundred GB into PostgreSQL (short of 100 tables and several hundred views). Apply primary keys then foreign keys to catch data/encoding corruption, create trigger shells and skeleton functions to compile then refactor, and iteratively rebuild views until only problematic definitions remain. Command‑line SQL Server clients on Linux validate ports, users and truncated catalog issues (2KB view storage).
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:46SUMMARY STEPS
- 2:42SUMMARY DETAILS
- 7:48The SECRET SAUCE
- 10:58System Catalog Vs Information Schema
- 12:07PREPARING THE TARGET DATABASE
- 14:21INSTALLING POSTGRES
- 15:19THE tds faw FOREIGN DATA WRAPPER
- 16:14CONNECTING PG AND MSSOLE
- 16:38IMPORTING TABLES
- 17:06PROCESSING FUNCTIONSISPRO
- 18:27MASSAGING POSTGRES
- 22:53POPULATE TABLES
- 23:25IMPORT SYSTEM CATALOGS
- 25:08POPULATE SYS CATALOGS
- 25:42PROCESS THE TRIGGERS
- 26:12PROCESS THE VIEWS
related talks
45mSQL Server to PostgreSQL: Migration Challenges & Solutions
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
46mPostgres for the SQL Server DBA
46mThe Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL
38mSwitching Teams: Moving an Application from MySQL to PostgreSQL
29mTales from the Field - Oracle to PostgreSQL migrations
34mPartitioning and Data Migrations Using PostgreSQL as an Example
06mMigration Consideration Oracle to PostgreSQL
