SQL Server
Oracle

SQL Server to Oracle Converter

Selected tables into an Oracle schema, with editable mappings for a one-time load or a scheduled synchronization job.

Version
5.4.0
Release Date
Oct. 25, 2026
Size
98.7 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Copy SQL Server tables into an Oracle schema. DBConvert proposes the Oracle column types, creates the selected tables, indexes, and foreign keys, and transfers rows through a live connection to each server.

  • Reads SQL Server, SQL Server Express, Azure SQL Database, or Amazon RDS for SQL Server.
  • Writes to Oracle Database 11.2 and later, including Oracle Database XE. The Oracle client ships with the application.
  • Runs on Windows as a desktop application.
  • The same download converts Oracle back into SQL Server.

Prepare a repeatable Oracle load

Connections, tables, and mappings remain available on separate screens as you prepare the job.

Limit the source data

Select individual tables and apply per-table row filters for a subset load rather than copying the whole database.

Choose the Oracle names

Fold table and column names to upper case, as Oracle stores unquoted names, or keep them as written. A table that already exists in Oracle is used under its own name.

Save the job

Reuse saved connections and keep the selected tables, mappings, and options for the next test run instead of entering them again.

Convert once, or keep Oracle in step with SQL Server

Conversion and synchronization are modes of one application.

One-time conversion

Create the Oracle tables and load their rows. Validate the data and run the application's queries before switching the write target.

Scheduled synchronization

Keep SQL Server in use while Oracle is prepared. A scheduled job sends inserts, updates, and deletes, one way or both ways, with explicit keys and conflict handling.

When Oracle is the right target

An application that runs on Oracle

Bring SQL Server data into a system or vendor package whose database is Oracle, and adjust the incoming columns to its schema.

Feeding an Oracle data store

Keep selected SQL Server tables copied into Oracle on a schedule for reporting or integration, without writing export scripts.

How SQL Server types map to Oracle

These are the defaults. Review or override the target type per column before the first load.

In SQL Server DBConvert default in Oracle What needs attention
Integers, BIT, DECIMAL, MONEY NUMBER at the matching width: INT as NUMBER(10,0), BIGINT as NUMBER(19,0), BIT as NUMBER(1,0), DECIMAL(p,s) as NUMBER(p,s), MONEY as NUMBER(19,4). Exact values stay exact, to the last digit.
VARCHAR, NVARCHAR, (MAX), TEXT VARCHAR2(n CHAR) and NVARCHAR2(n CHAR); VARCHAR over 4,000, VARCHAR(MAX), and TEXT become CLOB; NVARCHAR over 2,000, NVARCHAR(MAX), and NTEXT become NCLOB. Oracle treats an empty string as NULL. An empty value bound for a NOT NULL column is written as a single NUL character so the row still loads.
DATETIME, DATETIME2, SMALLDATETIME, DATE DATETIME and DATETIME2 become TIMESTAMP(6); SMALLDATETIME and DATE become DATE. Oracle keeps 6 fractional digits, so a DATETIME2(7) loses the last one.
TIME DATE on 1 January of year 1. Oracle has no time-only type. Fractions of a second are dropped; read the time part in queries.
DATETIMEOFFSET TIMESTAMP(6) WITH TIME ZONE, stored as the UTC instant. The moment is exact, but the original offset is not kept.
UNIQUEIDENTIFIER, XML, ROWVERSION VARCHAR2(36 CHAR) without braces, CLOB, and the 0x... text of the version. The application reads these as text; Oracle does not regenerate a ROWVERSION.
BINARY, VARBINARY, IMAGE, FLOAT, REAL RAW(n) up to a fixed width, BLOB for (MAX) and IMAGE; BINARY_DOUBLE and BINARY_FLOAT. No action needed; bytes and floating-point values are copied as they are.
IDENTITY and column defaults On Oracle 12c and later, an identity column (GENERATED BY DEFAULT) that continues after the copied keys. GETDATE() becomes SYSTIMESTAMP; numeric and text defaults are kept. On Oracle 11g the key stays a plain NUMBER. A function default such as NEWID() is dropped, not stored as text.

T-SQL and application SQL need a separate pass

DBConvert moves tables, columns, indexes, foreign keys, and rows. Stored procedures, triggers, functions, and views are not converted; rewrite them in PL/SQL and test them against the new schema.

Supported versions and services

SQL Server

  • SQL Server 2008-2022, including Express editions
  • Azure SQL Database and Amazon RDS for SQL Server
  • SQL Server schemas (dbo, custom schemas)
  • Windows authentication or SQL authentication

Oracle

  • Oracle Database 11.2 and later
  • Oracle client included in the installer

How to migrate SQL Server to Oracle

1

Setup: connect SQL Server and Oracle

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

The Setup step in DBConvert: the mode, the source and destination connections side by side, and the job name

SQL Server source

Connect by TCP/IP or Named Pipes, use Azure SQL, or read from Amazon RDS for SQL Server.

Oracle target

Enter the host, port and service name of the target database. Connect as SYSDBA only when the account requires it. See Oracle connection settings and Oracle connection issues.

Move SQL Server data into Oracle

Download the current build and run the first job against your own database.

Windows Windows 10 or later · 98.7 MB