The issue is organizational rather than technical.
Legacy applications aside, enterprises that have invested in Oracle has teams of Oracle skill sets in both development and operation. Furthermore, there are operating procedures that are Oracle specific.
All of these are costs of migration from Oracle. Yes, Oracle is SQL based. But you are locked-in once you invested heavily in it.
The way out: slow does it. Put together an PostgresSQL adaption strategy and do it case by case, leveraging opportunities when they present themselves.
At the end, it takes real commitment, just like getting off addiction or bad habits.
Slashdot Mirror
The issue is organizational rather than technical.
Legacy applications aside, enterprises that have invested in Oracle has teams of Oracle skill sets in both development and operation. Furthermore, there are operating procedures that are Oracle specific.
All of these are costs of migration from Oracle. Yes, Oracle is SQL based. But you are locked-in once you invested heavily in it.
The way out: slow does it. Put together an PostgresSQL adaption strategy and do it case by case, leveraging opportunities when they present themselves.
At the end, it takes real commitment, just like getting off addiction or bad habits.
Hint: EnterpriseDB may ease your pain.