Microsoft Connector for Oracle Support

A682945 — Mon, 09 May 2022 20:45:25 GMT

While upgrading to SQL Server 2019 from 2016, the Microsoft Connector for Oracle v 1.0 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. We still need the OLEDB connection to work so reordering the path isn't an option.

Also we login using a proxy account 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 Microsoft Connector for Oracle formerly Attunity.

Has anyone else experienced these issues? Thank you in advance

Gordon

topic Microsoft Connector for Oracle Support in Integration, Extension & APIs

Microsoft Connector for Oracle Support