Migrate Oracle to SQL Server

Prior to the migration, you should have a good understanding of your database workload including any key performance metrics and frequency of peak loads. The key to a proper comparison is a mechanism to replay a workload. You can achieve this through the SQL Server Distributed Replay feature or your own load harness.

Once under load, you can evaluate your new technology by monitoring pressure on CPU, Memory, IO Operations, and network traffic.

By monitoring when the system is under pressure you can determine if your technology is properly sized or if resources need to be adjusted.

DB Best can help you profile your existing environment and then grade your migration against that profile.

At first glance, an index is just another object in the database that needs to be migrated.  However, the manner in which data sits in storage is very different between Oracle and SQL Server.  DB Best approaches this circumstance by examining the logical layout of the tables and relationships, paying special consideration to the business needs and use cases of the underlying data to determine an appropriate indexing strategy.

One of the major factors to be considered when we migrate Oracle to SQL is licensing. In most cases, a SQL Server Standard edition may suffice. However, there are some key features of Enterprise Edition that should be considered which may have a big impact on the security, availability, manageability, and performance of your workload.

When it comes to scope there is a choice that must be made around how the conversion will proceed. The team will review all the source Oracle Schemas. Each Schema could either be migrated into its own isolated database or converted into a single database with multiple Schemas. We will work with you to consider the required security for isolation needs between the various Schemas.

There are several considerations for migrating an Oracle database. In addition to reviewing the Schemas in each Oracle instance, special attention needs to be paid to data type differences and incompatibilities.

For example, Numeric and date/time values are stored at different levels of precision and scale. Moreover, Oracle and Microsoft implement the SQL ANSI standards differently which may return different results.

It’s paramount that a QA team that is familiar with business needs and with the data review the code conversions from Oracle to SQL. Moreover, the QA team will need to verify that the converted code returns the expected data in the format and order that the business is accustomed to.