FIX: Errors may occur or PolyBase services fail to start when you run PolyBase queries on a non-English OS

Applies to: SQL Server 2019 on LinuxSQL Server 2019 on Windows

Symptoms


During PolyBase startup or when you run PolyBase queries on a non-English OS, you notice that the PolyBase queries fail and generate errors, or PolyBase services fail to start under certain conditions.

For example: 
When you try to start the PolyBase services in a Turkish locale, you receive the following error message:
 

"Could not load type 'Int' from assembly 'Microsoft.SQLServer.DataWarehouse.Common"

When you run PolyBase queries in a locale that uses commas instead of periods as decimal separators, you may notice the following:
  • Collecting sample statistics on a Teradata-backed external table does not use the percentage that is specified by the user.
  • Queries generate invalid float literals that generate an error from the external source.
  • Creating statistics over an external table that has a DateTime column returns the following error message:  "The string was not recognized as a valid DateTime."

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:

Workaround


To work around this issue, you can run PolyBase queries in English locale.

References


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