Sep 09 2019 10:36 PM
Sep 09 2019 10:36 PM
We have 64 bit SQL/Server with a 64-bit database (verified via a query that I found - thank you) and an Oracle 64-bit driver (latest version 19.3). I was successfully able to create an 64 bit ODBC connection and got the test connect to work. So far so good ...
Here is the version information in detail:
This is SQL/Server 13.0.5337.0 (2016?)
SSMS Version 17.4 installed on Windows Server 2016
Oracle 64 bit client version 19.3
When we go to create the linked server inside SSMS, the Oracle driver does not show up even though it shows up in the 64 bit ODBC manager and it works meaning that all the TNS stuff is properly set up (we are seasoned veterans setting those things up).
I read on a support site for DevArt's Sugar CRM systems that in order for 64 bit to be used, the database, SSMS, and the driver must be 64 bit. However, I also read that SSMS is still 32 bit and this was verified by running task manager and indeed it says it's a 32 bit app.
I certainly could switch to using the 32 bit version of the Oracle client, but I would rather not for future compatibility reasons down the road. The connection is very light weight and is only used to transfer very small (meaning single row) data back and forth between the two systems so this certainly would be easy work for a 32 bit ODBC connnection, but I was trying to future proof and go all 64 bit.
I have found bits and pieces of this answer, but all the questions are years old. We can update to a later version of SSMS if that is needed, I see 18.2 just got released and we certainly could use that as well. Had I realized SSMS was free now, I would have downloaded and installed it myself.
I do have full admin access to the Windows server system but not the database itself as that is managed by a DBA who didn't know the answer to this. I have set up linked servers before where I did have full DB privs (this is an upgrade situation), so I pretty much know what I want to do, just not sure how to do it and/or if it can be done.