Forum Discussion
SSMA Extension Pack for Oracle not compatible with ODBC 18
Hi Lain,
thank you very much for the prompt response -
actually I'm aware that ODBC Driver 18 also supports "no encryption" - it's an option that can be set in the connection string (Encrypt=No)
(and thank you for the hint about using encryption - we're also aware of this topic)
The problem is, that SSMA for Oracle also comes with an "Extension Pack" that needs to be installed on the server where the SQL
Server resides -
it provides DLLs that are then used by extended stored procedures that come with SSMA
Calling these xp_*-procedures obviously generates a new session
Unfortunately, there seems to be no way to set the "no encryption" option - or is there one?
The documentation unfortunately does not mention anything of the kind
Any help would be much appreciated
KR
Christian
Hi, Christian.
I'm afraid I cannot answer anything about SSMA. I'm approaching this more from the generic SQL Server and ODBC perspectives.
I would be curious to know if you can see any registered system or file DSNs though, which you can check through running both of the following commands:
- 64 bit: C:\Windows\System32\odbcad32.exe
- 32 bit: C:\Windows\SysWOW64\odbcad32.exe
If there are any interesting looking DSNs, you should be able to jump into the properties and adjust the two encryption-related settings there.
I won't get my hopes up though as I have not encountered a single reference to the use of ODBC in the SSMA documentation I've read so far (which isn't a lot). It's all been OLE DB provider references.
Cheers,
Lain
- Hi Lain,
thanks again for the fast response - and thank you for your time
The extension pack seems to require ODBC; so we seem to be left with options to either stick with
"ODBC Driver 17" (not good) or introduce encryption on SQL Server (with some impact)
Maybe Microsoft could add some hint about this issue in the docs of SSMA(?) Could possible help others
KR
Christian