Blog Post

SQL Server Integration Services (SSIS) Blog
3 MIN READ

Microsoft Connector for Oracle is released for SQL Server 2019 Preview

Tim.Chen's avatar
Tim.Chen
Icon for Microsoft rankMicrosoft
May 14, 2019
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...
Updated May 14, 2019
Version 1.0
gkmching's avatar
gkmching
Copper Contributor
Mar 22, 2022

Hi,

 

While upgrading to SQL Server 2019 from 2016, the Oracle adapter no longer recognizes the TNS service name in the Oracle connection manager editor.  Now we need to enter the ez connect text in it's place. 

 

The TNS service name connected when prioritizing the 32 bit oracle home path before the 64 bit path.  However once we did that the Oracle Provider for OLEDB connection stopped working.  

 

Also we use a proxy account to login to our oracle database to access objects located in our service account schema  (e.g. "username[service account]" ).  This allowed developers to use their login without knowing the service account password.  However that type of login doesn't work after upgrading to the new oracle adapter from attunity. 

 

Has anyone else experienced these issues?  Thank you in advance

 

***UPDATE after working with MS support.  This was the workaround:

Please try manually replacing the Oracle Connection Manager's connection string (in the connection manager properties) with a connection string in the following format and then confirm that proxy authentication works.

 

SERVER=;USERNAME=proxyuser;impersonateuser=usertobeimpersonated;pwd=proxypassword;WINAUTH=0;