Update: ODBC Driver 18.1.2 for SQL Server Released

DavidEngelMS Thanks for the great update. https://techcommunity.microsoft.com/t5/sql-server-blog/odbc-driver-18-2-for-sql-server-released/ba-p/3742780 . I can confirm that the memory leak has been eliminated.

The driver v18 and v17 crashes on Ubuntu 22.04. I see the application crashing with a segmentation fault on the call to SQLDriveConnectA(). The stack ends at:

libcrypto.so.3!OPENSSL_strcasecmp

Loaded '/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.1.so.2.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libdl.so.2'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/librt.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libodbcinst.so.2'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libkrb5.so.3'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libgssapi_krb5.so.2'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libpthread.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libk5crypto.so.3'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libcom_err.so.2'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libkrb5support.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libkeyutils.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libresolv.so.2'. Symbols loaded.
Loaded '/usr/lib/x86_64-linux-gnu/gconv/UTF-16.so'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libssl.so.3'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libcrypto.so.3'. Symbol

My application links OpenSSL 1.1.1n

ODBC Packages:

$ apt list --installed | grep odbc

libodbc2/jammy,now 2.3.9-5 amd64 [installed,automatic]
libodbccr2/jammy,now 2.3.9-5 amd64 [installed,automatic]
libodbcinst2/jammy,now 2.3.9-5 amd64 [installed,automatic]
msodbcsql17/jammy,now 17.10.2.1-1 amd64 [installed,automatic]
msodbcsql18/jammy,now 18.1.2.1-1 amd64 [installed]
odbcinst/jammy,now 2.3.9-5 amd64 [installed,automatic]
unixodbc-common/jammy,now 2.3.9-5 all [installed,automatic]
unixodbc-dev/jammy,now 2.3.9-5 amd64 [installed]
unixodbc/jammy,now 2.3.9-5 amd64 [installed,automatic]

gcc packages:

$ apt list --installed | grep gcc

gcc-11-base/jammy-updates,jammy-security,now 11.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
gcc-11/jammy-updates,jammy-security,now 11.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
gcc-12-base/jammy-updates,jammy-security,now 12.1.0-2ubuntu1~22.04 amd64 [installed]
gcc/jammy,now 4:11.2.0-1ubuntu1 amd64 [installed,automatic]
lib32gcc-s1/jammy-updates,jammy-security,now 12.1.0-2ubuntu1~22.04 amd64 [installed,automatic]
libgcc-11-dev/jammy-updates,jammy-security,now 11.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
libgcc-s1/jammy-updates,jammy-security,now 12.1.0-2ubuntu1~22.04 amd64 [installed]

Note: On the same environment the main.c sample application above by YOSHIZAKI_Shota works exactly as mentioned. Same memory leaks but no crash.

Only difference seems to be that my application links OpenSSL.

Good answer 

YOSHIZAKI_Shota Thanks for the details! This will be fixed in the next v18 release.

(Now I just need to figure out why/when I stopped getting email notifications of comments on my posts...)

I got some more details on the legacy "SQL Server"/"ODBC SQL Server Driver" driver issue from the Windows group:

Regarding ODBC legacy driver failing to query floating point columns, the fix should be available in Jan 2023, and customers can follow the status from the links below:

• https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-21h2#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2022#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-21h2#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-21h1#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-1809-and-windows-server-2019#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-1607-and-windows-server-2016#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-1507#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-8.1-and-windows-server-2012-r2#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2012#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-7-and-windows-server-2008-r2-sp1#2970msgdesc
• https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2008-sp2#2970msgdesc

As an alternative, you can update your application to use a driver under current development that doesn't have this issue. The Microsoft ODBC Driver for SQL Server is the latest: https://aka.ms/downloadmsodbcsql

This driver is NOT the same as the "SQL Server" ODBC driver that ships with Windows and is owned by the Windows team. This release of the "ODBC Driver 18 for SQL Server" would not have affected that driver. From what I've heard, the "SQL Server" driver was affected by a recent Windows update but I don't know any more details on that.

15delta, use a alternative driver ("SQL Server Native Client 11.0", "SQL Server Native Client 10.0") or simply cast the float columns to strings:

CAST(field AS VARCHAR(32))

Same here. Had to roll back the entire CU for half of our dev team who got this update over the weekend. Don't want to have to roll back the whole thing so if anyone has a suggestion for a workaround, would be much appreciated.

The same here, a lot of issues since November updates.

Same problem @juanrgm has stated.  This is breaking things for hundreds or thousands of our users.  We need a fix quickly!