FIX: DefaultLanguage.LCID property changes for partially contained In-Memory OLTP database

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core More


Assume that you have a partially contained SQL Server In-Memory OLTP (also known as Hekaton) database in an Always On Availability Group (AG) environment in Microsoft SQL Server 2016. If the database DefaultLanguage.LCID property is set to 1033, and you restart the database service or an Availability Group failover occurs, you find that the DefaultLanguage.LCID property is changed to 0.


This problem is fixed in Cumulative Update 4 for SQL Server 2016 Service Pack 2.


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


Learn about the terminology Microsoft uses to describe software updates.