FIX: "Culture is not supported" error or wrong results occur when you run PolyBase query in SQL Server 2019

Applies to: SQL Server 2019 on Windows

Symptoms


In SQL Server 2019you run a PolyBase query that meets the following criteria:
  • The result set has a VARCHAR(MAX) column.
  • Thequery has certain execution plan shape characteristics. For example, it has a globalaggregation.
In this scenario, you encounter the following problems:
  • If the column contains characterdata that cannot be encoded by using the current locale of the PolyBaseEngine process, or the result of the encoding that uses the current locale isdifferent from the encoding that is specified in the column's collation, you see incorrecttranslation of that character data. Specifically, untranslatable characterswill 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.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

Resolution


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:

References


Learn about the terminology that Microsoft uses to describe software updates.