In SQL Server 2019, you run a PolyBase query that meets the following criteria:
The result set has a VARCHAR(MAX) column.
The query has certain execution plan shape characteristics. For example, it has a global aggregation.
In this scenario, you encounter the following problems:
If the column contains character data that cannot be encoded by using the current locale of the PolyBase Engine process, or the result of the encoding that uses the current locale is different from the encoding that is specified in the column's collation, you see incorrect translation of that character data. Specifically, untranslatable characters will be replaced by a question mark (?).
If the PolyBase Engine process is running as a user and has a custom locale, you receive the following error message:
System.Globalization.CultureNotFoundException: Culture is not supported.
Parameter name: culture
3072 (0x0c00) is an invalid culture identifier.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Learn about the terminology that Microsoft uses to describe software updates.