Assume that you have dynamic data masking enabled in one or more tablesin Microsoft SQL Server 2016, 2017, or 2019. In rare scenarios, a locking conflict may occurduring error message processing, and SQL Server may terminate unexpectedly. Additionally, an error entry that resembles the following may be logged in the error log:
DateTime SpidId Stack Overflow Dump notpossible - Exception ExceptionId EXCEPTION_STACK_OVERFLOW at ExceptionAddress
DateTime SpidId ex_terminator: Possible termination due toexception during stack unwinding.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative updates for SQL Server:
- Cumulative Update 4 for SQL Server 2019
- Cumulative Update 20 for SQL Server 2017
- Cumulative Update 12 for SQL Server 2016 SP2
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:
To work around the issue, you can remove all data masking from tables.