Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Assertion occurs when TF 831 is turned ON/OFF multiple times in SQL Server 2019


View products that this article applies to.

Symptoms

When the Trace Flag (TF) 831 is turned ON/OFF multiple times in SQL Server 2019, you may receive an assertion error. Additionally, the Concurrent PFS Update feature switch runs into inconsistency because of the dependency on the TF 831.

↑ Back to the top


Status

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

↑ Back to the top


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:

↑ Back to the top


Workaround

To work around this issue, the TF 831 should be changed only during the startup so that the Concurrent PFS Update feature switch remains the same, and doesn't run into inconsistency. 

↑ Back to the top


References

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

↑ Back to the top


Keywords: kbqfe, kbfix, kbexpertiseinter, kbsurveynew, Concurrent PFS Update Feature in SQL Server 2019, kb, kbHotfixAuto, CI112880, kbnotautohotfix

↑ Back to the top

Article Info
Article ID : 4531702
Revision : 169
Created on : 2/15/2020
Published on : 2/15/2020
Exists online : False
Views : 448