Aug 23, 2011

What is the SQLDump file for?


One of our Windows 2003 servers that has WSUS is full on hdd space. Doing a search for files I find this SQLDump10000.txt file that is over 25gigs. I have done some googling and it says it’s read write errors plus the query or what was in memory. Can someone give me a straight explaination of what is going on here?


These dump files are created under two circumstances:

  1. A SQL Server ‘crash’ occurs – either an A/V, assert or some other uncaught code error. In this case the file is a memory dump, the size and contents of which are dependent on the problem that occured.
  2. You’re signed up for Watson error reporting and DBCC CHECKDB found corruptions in a database. In this case, the contents are the list of corruptions that were found and a dump of corrupt disk pages from memory

Can you look in the SQL error log to see an indication of something going wrong, with a timestamp in the error log around the same time as the creation time of the dump file?

As far as your transaction log being full – I would copy off the dump file somewhere else as it sounds like it’s messing up your log management. Don’t do anything like deleting the log file or anything like that, or you’re guaranteed to cause corruption.

Hope this helps

Related posts:

  1. Dump a linux process’s memory to file
  2. inadvertantly deleted memory.dmp file
  3. SQL Server Backup modes, and a huge log file
  4. SQL Server: Log file grows more and more, and do not get merged with the MDF file
  5. How can I use a batch file to dump only the last few weeks’ revisions in SVN?

Leave a comment