Assume that you have a database in Microsoft SQL Server 2016 or 2017 that has transparent database encryption enabled, or is in the process of being enabled ordisabled. If the database contains corruption such that a GAM extent isimproperly marked as unallocated in the GAM or PFS page for the extent, it ispossible for the encryption scan to incorrectly assume that the GAM page isunallocated, and then format the page. In this case, a subsequent restart of the server will cause the database to be marked suspect upon recovery, and you may receive thefollowing error message:
DateTime SPID Error: 5243, Severity: 16, State: 8.
DateTime SPID An inconsistency was detected duringan internal operation. Please contact technical support.
- This fix will prevent the encryption scan from formatting the corrupt GAM page, but it will not address the database inconsistency.
- If the customer is frequently pausing and resuming the encryption scan by using Trace Flag (TF) 5004, this issue may be more likely to occur, and you may see multiple dumps.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Cumulative Update Information:
This issue is fixed in the following cumulative updates for SQLServer:
- Cumulative Update 1 for SQL Server 2019
- Cumulative Update 18 for SQL Server 2017
- Cumulative Update 11 for SQL Server 2016 SP2
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all thehotfixes and all the security fixes that were included with the previouscumulative update. Check out the latest cumulative updates for SQL Server: