Home
Microsoft

Microsoft Connector for Oracle  is the replacement of Attunity Oracle Connector starting from SQL Server 2019 and now it is released for preview. Microsoft Connector for Oracle provides compatibility with Attunity Oracle Connector in functionality and performance. Packages designed with Attunity Oracle Connector can run with Microsoft Connector for Oracle without any changes.

 

Microsoft Connector for Oracle is supported in:

 

  1. SQL Server 2019

User can download Microsoft Connector for Oracle V1.0 (SQL Server 2019) - Preview for executing Oracle packages in SQL Server 2019. For Microsoft Oracle Connector, Oracle client is not required.

 

  1. SQL Server Data Tools (SSDT)

Microsoft Connector for Oracle has is shipped in SSDT for VS 2017 since version 15.9.0, as well as in SSIS projects for VS 2019. Users do not need extra installation of Oracle connector when designing packages targeting SQL Server 2019.

 

Using Oracle Connector in SQL Server Data Tools (SSDT) 15.9.x for VS 2017 or SSIS Projects for VS 2019

Microsoft Connector for Oracle has been shipped in SSDT for VS 2017 since 15.9.0 and SSIS Projects for VS 2019. User can use Microsoft Connector for Oracle to design packages targeting to SQL Server 2019 and pre-2019.

Design new SSIS packages

Open SSDT 15.9.x, Oracle components can be found in SSIS Toolbox, under Common Category.

1.png

And in Connection Managers, Oracle connection manager is displayed with type “ORACLE”.

2.png

Microsoft Connector for Oracle provides similar user experience with Attunity Oracle Connector. User can design new packages based on previous experience.

 

In design time, no matter which SQL Server version the project is targeting, no extra dependency is required to be installed. If user wants to use TNS service name in tnsnames.ora for connecting to Oracle Server, there are a few ways to achieve this:

 

  1. Install Oracle client and create tnsnames.ora in network\admin under Oracle client path. This is exactly the same with Attunity Oracle connector.
  2. Create tnsnames.ora under any local directory and add a TNS_ADMIN system environment variable which value is the tnsnames.ora directory path.
  3. Create tnsnames.ora under any local directory and set the direct path to OracleHome property in Oracle connection manager advanced editor.

 

Open and Execute existing SSIS packages

Existing SSIS packages which have been designed with Attunity Oracle Connector will be automatically upgraded to use Microsoft Connector for Oracle. The icons will be changed as well.

 

After successfully opening existing packages, users can redesign or execute package, or change the target SQL Server version for the project.

 

Execute SSIS packages

Execute packages targeting SQL Server 2019

If the project is targeting SQL Server 2019, there is no extra dependency for execution. Oracle client is not required. User can directly execute and debug package.

 

Execute package targeting Pre-SQL Server 2019

If the project is targeting Pre-SQL Server 2019, corresponding Attunity Oracle Connector and Oracle client are required to be installed on the SSDT machine for package execution.

 

Attunity Oracle Connector download links:

The required Attunity Oracle Connector and Oracle client platform version depends on project debug config, as the picture shown.  

3.png

If Run64BitRuntime is set to True, x64 version Attunity Oracle Connector and Oracle client are required to be installed.

If Run64BitRuntime is set to False, x32 version Attunity Oracle Connector and Oracle client are required to be installed.

 

Some FAQs:

 

  1. Exception from HRESULT: 0xC0011001 when opening existing package

It is a known issue in SSDT 15.9.0 and 15.9.1, when package uses features like Expressions in the connection manager. User can remove Expressions as a workaround. The issue will be fixed in next SSDT release (15.9.2).

 

  1. Cannot connect to Oracle Server

When using TNS service name in tnsnames.ora, user may encounter this error if the environment is not set right. There are few ways to fix:

  1. Add TNS_ADMIN to system environment variable, which value is the path of tnsnames.ora file.
  2. Set OracleHome and OracleHome64 in Oracle connection manager to tnsnames.ora path in x86 and x64 Oracle client respectively.
  3. Use format [//]host[:port][/service_name] in the TNS service name field in connection manager to connect instead.

 

  1. Exception deserializing the package "Value does not fall with the expected Range" when running package

This will happen in package execution if package is targeted to pre-SQL Server 2019, and corresponding Attunity Oracle Connector is not installed. Just install the corresponding Attunity connector to mitigate the error.

1 Comment
Occasional Visitor

Thi is really a cool , so now SQL2019 can cun any Oracle Packages using connector?