ETL SQL Server in Oracle Data Integrator

Ready to get started?

Download for a free trial:

Download Now

Learn more:

SQL Server Driver

Rapidly create and deploy powerful Java applications that integrate with Microsoft SQL Server.



This article shows how to transfer SQL Server data into a data warehouse using Oracle Data Integrator.

Leverage existing skills by using the JDBC standard to read and write to SQL Server: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for SQL Server connects real-time SQL Server data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with SQL Server just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the SQL Server APIs in real time instead of working with flat files.

This article walks through a JDBC-based ETL -- SQL Server to Oracle. After reverse engineering a data model of SQL Server entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR and .lic file, located in the installation folder, into the ODI userlib directory:

On Unix: ~/.odi/oracledi/userlib On Windows: %APPDATA%\Roaming\odi\oracledi\userlib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of SQL Server data. After reverse engineering, you can query real-time SQL Server data and create mappings based on SQL Server tables.

  1. In ODI, connect to your repository and click New -> Model and Topology Objects.
  2. On the Model screen of the resulting dialog, enter the following information:
    • Name: Enter SQL.
    • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
    • Logical Schema: Enter SQL.
    • Context: Select Global.
  3. On the Data Server screen of the resulting dialog, enter the following information:
    • Name: Enter SQL.
    • Driver List: Select Oracle JDBC Driver.
    • Driver: Enter cdata.jdbc.sql.SQLDriver
    • URL: Enter the JDBC URL containing the connection string.

      Connecting to Microsoft SQL Server

      Connect to Microsoft SQL Server using the following properties:

      • Server: The name of the server running SQL Server.
      • User: The username provided for authentication with SQL Server.
      • Password: The password associated with the authenticating user.
      • Database: The name of the SQL Server database.

      Connecting to Azure SQL Server and Azure Data Warehouse

      You can authenticate to Azure SQL Server or Azure Data Warehouse by setting the following connection properties:

      • Server: The server running Azure. You can find this by logging into the Azure portal and navigating to "SQL databases" (or "SQL data warehouses") -> "Select your database" -> "Overview" -> "Server name."
      • User: The name of the user authenticating to Azure.
      • Password: The password associated with the authenticating user.
      • Database: The name of the database, as seen in the Azure portal on the SQL databases (or SQL warehouses) page.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the SQL Server JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.sql.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      Below is a typical connection string:

      jdbc:sql:User=myUser;Password=myPassword;Database=NorthWind;Server=myServer;Port=1433;
  4. On the Physical Schema screen, enter the following information:
    • Schema (Schema): Enter SQL.
    • Schema (Work Schema): Enter SQL.
  5. In the opened model click Reverse Engineer to retrieve the metadata for SQL Server tables.

Edit and Save SQL Server Data

After reverse engineering you can now work with SQL Server data in ODI. To edit and save SQL Server data, expand the Models accordion in the Designer navigator, right-click a table, and click Data. Click Refresh to pick up any changes to the data. Click Save Changes when you are finished making changes.

Create an ETL Project

Follow the steps below to create an ETL from SQL Server. You will load Orders entities into the sample data warehouse included in the ODI Getting Started VM.

  1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

    Alternatively you can use SQLPlus. From a command prompt enter the following:

    sqlplus / as sysdba
  2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the Orders table in SQL Server: CREATE TABLE ODI_DEMO.TRG_ORDERS (FREIGHT NUMBER(20,0),ShipName VARCHAR2(255));
  3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
  4. Click Reverse Engineer. The TRG_ORDERS table is added to the model.
  5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
  6. Drag the TRG_ORDERS table from the Sales Administration model onto the mapping.
  7. Drag the Orders table from the SQL Server model onto the mapping.
  8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
  9. Open the Physical tab of the Mapping Editor and click ORDERS_AP in TARGET_GROUP.
  10. In the ORDERS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load SQL Server data into Oracle.