Symptoms

Assume that you use Microsoft SQL Server 2016 and 2017, and you have a database that uses ColumnStore tables. When you run the function sys.fn_dump_dblog against transaction log backup (*.TRN) files, you may notice that Access violation occurs.

Msg 0, Level 11, State 0, Line LineNumber

A severe error occurred on the current command.  The results, if any, should be discarded.


Here is an example of the sys.fn_dump_dblog command:

select *

from sys.fn_dump_dblog('0x0014e87d:0000f322:0053', NULL, NULL, 1,

'FileName\FilePath'

,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,

NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,

NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL)

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 updates 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:

References

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×