THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | Join | Help
in Search

Kevin Kline

SQLDumper

You might recall my recent posting about getting minidumps from SQL Server.  Even if you’ve never looked for dumps from SQL Server, you should get familiar with SQLDumper.exe.  SQLDumper is an internally called process that can produce a stack dump in mini, full, and filtered formats.  SQL Server has a default approach to how it does dumps, but you can alter this default behavior by starting SQL Server using trace flags ranging from 2540 to 2559.  (You should do so only under the advice of PSS, btw.)

 

Although SQLDumper can crank out a stack dump from any application, I recommend you stick with SQL Server.  Also, don’t plan on using SQLDumper as general purpose dumping utility.  Check out Microsoft’s recommendation for general purpose debugging at http://www.microsoft.com/whdc/devtools/debugging/default.mspx.

 

However, you can learn more about how and when to use SQLDumper with these resources:

 

·         http://support.microsoft.com/kb/917825 - How to use SQLDumper to generate dump files in SQL Server 2005

·         http://support.microsoft.com/kb/827690 - How to use SQLDumper to generate dump files for Windows Applications

 

That doesn’t mean that its easy to get SQLDumper working for you.  About the only way I’ve seen that you can get really good with SQLDumper is to have the unfortunate occurrence of needing it – i.e. lots of crashes.

 

If you have any experience with working with SQLDumper, I’d love to hear your feedback here.

 

Best regards,

 

-Kevin

 


Published Thursday, December 20, 2007 2:18 PM by KKline
Filed under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Jason Haley said:

December 21, 2007 12:01 PM
 

KKline said:

Thanks for the trackback, Jason.

-Kev

January 2, 2008 12:40 PM
 

Kyle Goodnight said:

I have never(knowingly) used SQLDumper. Recently I am getting a boot time message saying SQLDumper has been tampered with and should be reinstalled. What causes this message and how may I rid myself of it. It does not seem to impact my system (Xppro sp2) that I can see but I do not like having a boot issue like this that I do not know how to fix.  

Thanks in advance for any info you may be able to provide.

Kyle

kyler@kylekraft.com

January 17, 2008 10:54 PM
 

KKline said:

Hi Kyle,

I'm not sure what the cause of the problem is, but I'm guessing that you installed it or some software you're using installed it for you with SQL Server 2005 Express.  Reinstalling SQL Server 2005 Express will fix the issue.

Other solutions include:

  a. Stopping and disabling the SQL Server VSS service (if you're not using it).

  b. Reinstalling the SQL Server native client (if you are using it), found at http://msdn2.microsoft.com/en-us/data/aa937733.aspx.

Hope this helps,

-Kevin

January 23, 2008 11:01 AM
 

Zunanji viri said:

Update: New Stuff from the latest update will be in RED . This list will grow as I find new tools. So

February 6, 2008 5:28 PM
 

∈鱼杆 said:

FreeSQLServertoolsthatmightmakeyourlifealittleeasierUpdate:NewStufffromthelatestu...

July 25, 2008 4:00 AM
 

挥辉 said:

FreeSQLServertoolsthatmightmakeyourlifealittleeasier

Update:NewStufffromthelatest...

September 13, 2008 12:08 PM
 

Duc Tran said:

Would you know where I can find some documentation on how SQL Server by default does dumps?

I am currently implement a process to alert when a dump happens on production server. we want to react as soon as we find out it happens.

What we are thinking is to set location of the dump file to a dedicated folder and monitor it thru some tool (SQL agent or other 3rd party tool..etc). The question is how much disk space we have to make sure available to allow dumping finishes successfully.

Thank you in advance.

Duc Tran

November 18, 2008 4:09 PM
 

KKline said:

Duc,

I don't know off the top of my head where the dump file will be located.  However, you can reference the KB articles for general information about file placement or run a test to find where the file goes by default.  Once you learn that, please post here for everyone's edification.

Many thanks,

-Kevin

December 14, 2008 6:48 PM
 

Duc Tran said:

Location of the dump file can be set thru Advanced option "Dump Directory" of SQL Engine Service. You can get there by:

1) Open SQL Server Configuration Manager (SSCM)

2) Select SQL Server Services node on the left pane

3) Find the SQL Engine Service of the SQL instance you want to setup and right click to select "Properties".

4) In "Advanced" tab, you will see "Dump Directory" option

Factory Default location is under installation location of the SQL instance (C: drive unless you picked differently during installation).

Dump files could be quite big sometimes so it is good idea to plan ahead and move it out to a dedicated location with a good side of free space. The last thing you want to see is your production server has an issue and fails to generate dump files or generates an imcomplete dumps. Dump files are very resourcefull piece of information that are asked by Microsoft support staff when you contact them.

My question originally for this blog is How much disk space should we plan for this dump location? Also by default (factory default), which type of dump files (mini, full, filtered?) SQL Server generates in which situation? I am interesting in any documentation that may give us this answer if there are any out there or from Microsoft.

Thank you,

Duc Tran

January 7, 2009 12:57 PM

Leave a Comment

(required) 
(optional)
(required) 
Submit

About KKline

Kevin Kline is Technical Strategy Manager for the SQL Server business unit at Quest Software. Kevin was the original architect and dev manager for many of Quest's SQL Server tools. Prior to Quest, Kevin worked as an enterprise DBA for a variety of large corporations and government agencies.
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement