Convert Oracle to SQL Server.

A large number of mid and large-sized companies currently utilize Oracle on-premise databases as part of their overall IT infrastructure. As the volume of data in the database ecosystem continually increases, it requires better management and more expensive storage.

One of the possible solutions is to migrate Oracle data to SQL Server (hosted in Azure SQL cloud or on-premise).

SQL Server Migration Assistant for Oracle (Oracle2SQL) from Microsoft serves such kind of tasks. Migrating Oracle to SQL Server using SSMA is possible in ONE direction only.

You should be aware that there are several different usage scenarios for SSMA alternative - DBConvert migration tools:

  1. DBConvert tool minimizes challenges you can meet when migrating from Oracle to SQL Server. Your database schemas, tables, views, and relations will be migrated accurately and rapidly according to the requirements of the target database, preserving database consistency.
  2. After making a copy of your source database to target DB, keep your databases in Sync with Update, Insert, and Drop synchronization features.
  3. You can configure a DBSync windows application to perform bidirectional replication between Oracle and SQL Server (where two different databases simultaneously replicate changes from each other).

Four steps to migrate Oracle to SQL Server.

  1. Connect to the source Oracle database that you want to migrate. Once connected, DBConvert program obtains metadata about Oracle objects and displays them on the customization step later.
  2. Connect to destination on-premises SQL Server or a cloud MSSQL instance on Azure SQL DB/ Azure SQL Data Warehouse, Amazon RDS, or Google Cloud SQL for SQL Server.
  3. Pick tables, indexes, foreign keys, and views or select all to convert the whole database from the Oracle to SQL Server, Azure.
  4. Migrate, or Sync Oracle database objects to the destination on-premises SQL Server or instance in the clouds.

Note: Your connections to source and destination servers stay active until you close DBConvert software or open new connections on "source"/ "destination" steps.

Benefits of using DBConvert software.

  • ✅ In any combination, data migrations between Oracle, Microsoft SQL Server, Windows Azure SQL Databases/ Azure SQL Data Warehouse, AWS RDS, or SQL Cloud for SQL Server are possible. Please refer to the list of available conversion and sync directions in product info cards on the top.
  • ✅ Because the Oracle and SQL Server data types are different, DBConvert software automatically assigns a data type for the target database. With Data Type Mapping, you can easily match Oracle data type to its closest relative equivalent in the SQL Server target fields.
  • ✅ On the customization step, an smart error checker verifies all possible data integrity issues and highlights them, if any, before performing a migration.
  • ✅ Syntax of SELECT-queries of Oracle views and MS SQL is similar but not the same. DBConvert application can Convert Oracle queries to SQL Server format.
  • 🚫 We do not convert Oracle functions to SQL Server.
 DBConvert for Oracle & MSSQL

Migration directions:

  • Oracle ↔ SQL Server
  • Oracle ↔ Azure SQL DB | Azure SQL Data Warehouse
  • Oracle ↔ Amazon RDS ↔ SQL Server
  • Oracle ↔ Google Cloud SQL for SQL Server
  • ☑ Migrate to SQL Server Dump | Oracle Dump
  • ☑ Oracle views ↔ SQL Server views

Version: 2.1.4

Release Date: Feb. 12, 2020

 DBSync for Oracle & MSSQL

Sync directions:

  • SQL Server ↔ Oracle
  • Azure SQL DB | Azure SQL Data Warehouse ↔ Oracle
  • SQL Server ↔ Amazon RDS ↔ Oracle
  • Google Cloud SQL for SQL Server ↔ Oracle

Version: 1.4.1

Release Date: Nov. 14, 2018

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 1.8.4

Release Date: Nov. 23, 2020

Supported databases:

  • SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Firebird
  • Excel
  • IBM DB2
  • Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Using Oracle to SQL Server conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to Oracle source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to Oracle source database from DBConvert

2. Connect to SQL Server destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to SQL Server target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • Oracle to SQL Server
  • SQL Server to Oracle
  • Oracle to Oracle
  • SQL Server to SQL Server

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the SQL Server destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from Oracle to SQL Server.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source Oracle database to the closest equivalent of the target SQL Server database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from Oracle to SQL Server

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps Oracle source and SQL Server target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\oracle2mssqlPro\oracle2mssqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

Requirements

  • Necessary privileges to write into database on the target SQL Server (this requirement is optional as there is an option to overcome the restrictions using dump file)
  • Necessary privileges to write into database on the target Oracle server (this requirement is optional as there is an option to overcome the restrictions using dump file)
  • Oracle 12.x versions require Oracle Database 12c Release 2 Client (12.2.0.1.0) for Microsoft Windows (32-bit) to be installed: