Zhivko Todorov
ALL CASE STUDIES

CASE 19 · KESTREL · 2024

ORACLEAURORA POSTGRESDMSSCT

Oracle to Aurora Postgres, no leftover PL/SQL.

An order management platform had a 2.4TB Oracle database with 380 stored procedures and a five-figure monthly licence. We migrated to Aurora Postgres with Schema Conversion Tool plus a careful refactor of the PL/SQL — and finished the engagement with zero remaining Oracle dependencies.

INDUSTRY

Order management

DOMAIN

MIGRATION

DELIVERED

2024

STACK

AWS DMS·SCT·AURORA POSTGRES·AURORA SERVERLESS V2·CDC·PERFORMANCE INSIGHTS

RESULTS

What changed, by the numbers.

LICENCE SAVINGS

$340K/yr

NET OF AURORA COST

PROCEDURES MIGRATED

380 → 0

PORTED OR DELETED

p99 QUERY LATENCY

−18%

POST INDEX REBUILD

CUTOVER WINDOW

22m

CDC TAIL CLEAN

HOW IT WENT

The first finding was that 90 of the 380 stored procedures were unused — nothing in the application called them. We deleted those. SCT handled the mechanical conversion of the remaining 290; about 60 needed manual review for PL/SQL idioms PostgreSQL handles differently (mostly array handling and date arithmetic).

DMS did the bulk load and the CDC tail. Aurora Serverless v2 absorbed the variable production load with auto-scaling between 4 and 32 ACUs. Performance Insights showed the bottleneck moving from connection pool exhaustion (the Oracle pain point) to a single missing index, which we added.

Cutover ran on a Sunday at 02:00 UTC. DMS validated 1.6 billion rows; we had a sub-second CDC tail at the flip. The application connection string changed; nothing else did. The Oracle support ticket queue went quiet, then closed.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →