When a memory dump file is generated either by user or by SQL Server under certain conditions in SQL Server 2014 RTM version, SQL Server error log incorrectly reports an informational message that resembles the following:

<Date><Time> spid#       Server was configured to produce dump on the following event - ex_dump_if_requested: Exception raised, major=2, minor=8, state=1, severity=25, attempting to create symptom dump
<Date><Time> spid#      **Dump thread - spid = 0, EC = 0x000000084F2BAAD0
<Date><Time> spid#       ***Stack Dump being sent to <File Path>\<File Name>.txt
<Date><Time> spid#       * *******************************************************************************
<Date><Time> spid#       *
<Date><Time> spid#       * BEGIN STACK DUMP:
<Date><Time> spid#       *   <Date><Time> spid#
<Date><Time> spid#       * Private server build.

Note You can repro the issue by using the following commands:

dbcc dumptrigger('set',208)
select * from foo
dbcc dumptrigger('clear',208)


The issue occurs because of a defect in SQL Server 2014.

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:


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

Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!