Convert SQL Server to Oracle.

Our DBConvert/ DBSync solutions will convert and synchronize your SQL databases and Oracle databases.

These applications quickly move your data from MS SQL server/ Windows Azure SQL databases to Oracle server and conversely.

Our software reduces the risk of data migration loss by employing a secure and reliable migration methodology. Applications give preemptive messages about possible conversion and synchronization errors before starting the actual execution process. In just a ew easy steps your database migration project will be successfully completed.

You can customize all conversion and synchronization processes, adjusting the tools to your specific requirements. Data export and import may be full or partial. The tools allow moving not only the entire database but also the separate elements including tables, fields, primary keys, primary constraints and indexes.

Conversion to Dump files, in addition to direct conversion to a target server, is supported in the DBConvert tool.

DBSync for MSSQL and Oracle reliably and rapidly synchronizes your database from MS SQL Server or Windows Azure SQL databases to Oracle servers and conversely.

DBSync has insert, update and drop synchronization. Boost your database synchronizations using our trigger-based sync feature and you’ll notice that the processing speed is much faster.

Our applications support automatic job launching with the help of our built-in scheduler. They also support command line operation.

Different types of synchronization are also available for keeping your databases up-to-date.

 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.3

Release Date: Oct. 17, 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 SQL Server to Oracle 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 SQL Server source database.

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

Connect to SQL Server source database from DBConvert

2. Connect to Oracle 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 Oracle 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:

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

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 Oracle 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 SQL Server to Oracle.

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 SQL Server database to the closest equivalent of the target Oracle 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 SQL Server to Oracle

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 SQL Server source and Oracle 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 Oracle 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 SQL 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: