SSMS doesn't use ODBC drivers to connect to SQL Server databases. It uses the .Net Framework driver.
You cannot choose which driver it uses as it is hard-coded in the application. But why would you need to choose another one?
Linked servers are another thing. It is your DB Server itself connecting to another server. If it is SQL Server, it will use its ...
I came to a solution, if anyone is interested:
For any reason, firebird ODBC 64-bits driver downloaded from oficial site comes with SQLLEN = 4 bytes. After some help, I managed to compile driver from source code, and the result seems to work with 8 bytes SQLLEN.
In the compile proccess, I had a BUILD_DRIVER_VERSION error, modifying line 139 (...
When you launch your app using "runas" command, you use some domain user, and that user has Windows login at your SQL server. Or that domain user is part of some AD group that has Windows login at your SQL Server
When you launch app without "runas" command, the app is running, but under different security context (under different windows user), right ?
Use a signed stored procedure. The right to alter logins is encapsulated within the SP. The users only have rights to execute the SP, not amend logins directly. You may need several SPs to cover different aspects for administration.
how safe is this remote SQL Server access scheme
The shared account credentials embedded in the application can be read by anyone who controls a computer on which the application runs. No matter how you try to hide the credentials, you can never hide from a user with a debugger, who can just set a break point on the function that handles the password and ...
After bashing my head for a good while, I could make the ODBC 32 bits run. It was the VC ++ 2013 Redistributable.
My install is version 220.127.116.11.0. I can't believe how stupidly hard it is to get the simple ODBC. You must uncompress the Instant CLient plus ODBC in the same folder and then manually install VCRedist to get this running. GEEEZ.
I would consider moving away from MS Query/ODBC in general, and start using PowerQuery and yes, learn some of the "M" Language too. Excel is moving away from ODBC (my hunch from other blogs. Nothing official yet) and old DLL-style technologies, so it's worth catching up and going from there. Also you might consider PowerBI and really step away from ...
Old, but for those searching, as me recently ;) Part of documentation section 4.1:
Make sure the Visual C++ Redistributable for Visual Studio is installed.
• Connector/ODBC 8.0.14 or higher: VC++ Runtime 2015 or VC++ Runtime 2017
• Connector/ODBC 8.0.11 to 8.0.13: VC++ Runtime 2015
• Connector/ODBC 5.3: VC++ Runtime 2013
Use the version of ...
Microsoft fixed this issue in Cumulative Update 4 for SQL Server 2014.
If you are unable to install the update, they provide a workaround:
To work around this issue, use a nested loops join or a hash join by
using the Option command instead of the merge join.