The document discusses migrating from Oracle to Postgres in the cloud using EnterpriseDB's (EDB) Postgres Cloud Database Service. It highlights that EDB offers Oracle compatibility, migration tools, and human support to help with migrations. Over 50% of migrations have slight to no modifications needed. The presentation covers the EDB Cloud Database Service, reasons to migrate, components of a successful migration, what EDB offers to help, and how to identify good candidates for migration. It recommends leveraging the EDB tools and cloud database service for an agile migration.
Database migration strategies
Creating highly available clusters with EDB’s Cloud Database Service (CDS)
Live demo of migrating an Oracle database to EDB Postgres
$50 Credit
EnterpriseDB® (EDB™), the database platform company for digital business
Delivers a leading open source-based data platform for
- New applications
- Cloud re-platforming
- Application modernization
- Legacy migration
We sell the only complete database platform based on the open source Postgres.
The platform includes server software, enterprise management tools, training, services and support.
So, it is no surprise that EDB continues, for the fifth consecutive year, to be recognized among elite database vendors in Gartner Magic Quadrant for OPDBMS.
The power of EDB Postgres comes from its technologies and capabilities that offer interoperability, flexibility, and greater control for enterprise customers.
The EDB Postgres Platform rivals traditional vendor offerings for features and performance; yet as an open source-based provider, offers dramatic cost savings and greater flexibility.
EDB is now the only open source-based relational database vendor in the Gartner Magic Quadrant.
IDC Report talking points
“Help you Sleep at Night” concept
Speed
Security
Performance
Agility
Flexibility
Lower TCO
Worldwide support & services
1. Good candidates
1. Connects via JDBC
2. The app uses an ORM, such as Spring or Hybernate
3. The stored procedures are written in PL/SQL, not in Java or PL/C
4. # of concurrent active connections to the database < 1000
5. DB Size < 5 TB
6. Limited use of XML (XPATH, XMLDOM)
7. Application source code and application developers are available
8. No use of RAC for scalability
9. No need for Flashback
2. Really bad migration candidates:
1. ProC interface
2. Stored procedures written in Java
3. Must have RAC capabilities and Flashback
3. Moderate candidates
1. OCI interface
2. Oracle extensions of .NET and ODBC
1. Good candidates
1. Connects via JDBC
2. The app uses an ORM, such as Spring or Hybernate
3. The stored procedures are written in PL/SQL, not in Java or PL/C
4. # of concurrent active connections to the database < 1000
5. DB Size < 5 TB
6. Limited use of XML (XPATH, XMLDOM)
7. Application source code and application developers are available
8. No use of RAC for scalability
9. No need for Flashback
2. Really bad migration candidates:
1. ProC interface
2. Stored procedures written in Java
3. Must have RAC capabilities and Flashback
3. Moderate candidates
1. OCI interface
2. Oracle extensions of .NET and ODBC