Leaving Oracle and SQL Server for PostgreSQL: What Could Go Wrong
October 20–23
Moving away from Oracle or SQL Server is rarely just a database migration. The database is tied to applications, data models, integrations, operational processes, and years of database-specific decisions. That is where most of the complexity, risk, and unexpected cost comes from. The goal is not to argue that every Oracle or SQL Server workload should move to PostgreSQL. It is to show how to understand the work involved, reduce surprises, and make the migration a business decision rather than a leap of faith. If migrating to PostgreSQL is on your horizon, this talk is for you. We’ll take a look at what it really takes to make the move, and what to understand before migration begins. What will actually move cleanly? Where are the compatibility gaps? What needs to change in the application? And does the expected cost saving justify the effort? The practical work starts with assessing Oracle and SQL Server environments, planning migrations at scale, and validating the result along the way
