3 ms·
Depends on the complexity of their schema, and how many and of what complexity any stored procedures they relied on were.
by tracker1 13y ago
Depends on the complexity of their schema, and how many and of what complexity any stored procedures they relied on were.
- DrJokepu 13y agoIn many ways PostgreSQL is fairly similar to Oracle and it also supports its own version of PL/SQL. There are tools to automate migration of both schema and data. I reckon the real difficulty of such a transition is updating application code (and legacy code) to work with PostgreSQL.
- midas007 13y agoThis is by design because EnterpriseDB (based on Postgres) is basically intended as a replacment for Oracle. Anything commercial that uses fancy Oracle features would want to look at this because it would be easier to support.
- raverbashing 13y agoThis is the real story "Migrating from Oracle to PSQL" means almost nothing (from a technical point of view) But what were the issues? How did their schema look like then and now? Any stored procedures? Any Oracle-only features that had to be migrated? Any PSQL-only features now being used?
- diminoten 13y agoHaving worked on this team (QA side) for 3 years, I'm "just guessing" this was a big effort. Very cool Mark Kosters and Andy Newton gave the dev team the bandwidth to do this, their plates are almost always full of new features and whatnot.