Operational Defect Database
BugZero found this defect 657 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 14874191
KB5016780 - Improvement: Provide the closest matching non-UTF8 collation for the client drivers that don't support UTF-8 - Microsoft Support
Last update date:
8/11/2022
Affected products:
SQL Server 2019 on Linux
SQL Server 2019 on Windows
Affected releases:
build lower than 15.0.4249.2
Fixed releases:
15.0.4249.2
Description:
Summary
Microsoft SQL Server provides collation of the currently active database for the client drivers that don't natively support UTF-8. When an active database is collated by using a UTF-8 collation, the collation value is transmitted to the client driver verbatim. However, those client drivers can't support the collation. The passed collation value is used by the client drivers for encoding remote procedure call (RPC) parameters. This might cause incorrect bindings of CHAR or VARCHAR query parameters. This improvement enables SQL Server to send the closest matching non-UTF8 collation to the client drivers that don't natively support UTF-8. Therefore, the RPC parameters will be encoded correctly.
More information
This improvement is included in the following cumulative update for SQL Server: Cumulative Update 17 for SQL Server 2019 Note This update is disabled by default and can be enabled by turning on the trace flag 11813. For the best experience in working with UTF-8 databases, you should upgrade the client driver to the versions that natively support UTF-8. If the closest non-UTF8 collation uses the encoding that can't represent all characters in the bound parameter value, a data loss during parameter binding is still possible. For information about how to get the latest client drivers, visit Connection modules for Microsoft SQL Database.
References
Learn about the terminology that Microsoft uses to describe software updates.
