Sqldummper.exe is the SQL Server utility that can take the memory dump for the SQL server. After taking the memory dump, we can load it using the winDbg to see the internal call for trouble shooting.
Sqldummper comes with the sql server install and you can find it in the common shared folder.
SQLServerInstallDrive:\Program Files\Microsoft SQL Server\number\Shared
Note In this folder path, number is a placeholder for one of the following:
- The folder name is 110 for SQL Server 2012.
- The folder name is 100 for SQL Server 2008.
- The folder name 90 for SQL Server 2005.
Here is the example to take the mini memory dump and put the dump file in the C:\temp
- Full dump file :
Sqldumper.exe ProcessID 0 0x01100
- Mini-dump file
Sqldumper.exe ProcessID 0 0x0120
- Mini-dump file that includes indirectly referenced memory
Sqldumper.exe ProcessID 0 0x0120:40
- Filtered dump file
Sqldumper.exe ProcessID 0 0x8100
By default, if we don’t specify the dump directory, it will put the dump file in the current folder.
Windbg is the application that we can use to attach to the process or open the memory dump.
Setup symbol file source
open Crash dump
The file I open here is just a mini dump therefore it does not have much information .
- Viewing the Call Stack in WinDbg: http://msdn.microsoft.com/en-us/library/windows/hardware/ff539042(v=vs.85).aspx
- Common WinDbg Commands : http://www.windbg.info/doc/1-common-cmds.html
- How to use the Sqldumper.exe utility to generate a dump file in SQL Server: http://support.microsoft.com/kb/917825