Can i delete sql dump.mdmp files

Hope this will help you, Thanks. Improve this answer. Mayuresh Jadhav Mayuresh Jadhav 72 2 2 bronze badges. I would like to add: The age of the files - If your log folder has several dumps from two years ago, then no dumps for several months, then a few recent dumps, you can safely delete the two year old dumps. Here's a very good article with step by step instruction to resolve this issue. You may want to add salient points from the linked page to your answer directly, lest it becomes useless once the link goes stale.

Thanks — kiran. The way it is creating dump I have hunch that you are running SQL Server which is not patched to latest SP Scenario 2 If the SQL Server is patched to latest SP and still it is crashing producing stack dumps I would suggest you to open case with Microsoft they are the best in terms of analyzing the stack dump file and would surely tell you the reason.

I can share with you few blogs which would give you some hint on how to analyze the dumps Looking into SQL Server Minidump File How to analyze deadlock scheduler dumps Analyzing non yielding resource monitor Scenario 3 Not all crash dumps are because of bug in SQL Server many occur due to poorly configured SQL Server or some rouge queries running.

If you really like to delete it, delete the old ones and leave the new ones. Shanky Shanky I've started the bounty. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Linked 1. It is production. However, the server has some issues and it does hang from time to time. As a result, there are quite a few minidump. If yes, Can I delete these. Attachments: Up to 10 attachments including images can be used with a maximum of 3. Hi abhishekghosh ,. Personally, I prefer using the disk cleanup to avoid any bad handling.

You will find more details in the following post may help you:. Here is an image taken from one of my clients who contacted me for assistance.

First two files can be opened using notepad or any other text editor. Here is little information about them. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request.

Windows NT 6. If you see something like below, then its due to corruption in the database. If it is anything like below, then make sure you have applied the latest service pack and a cumulative update of SQL Server. There are high chances that it might be an issue with SQL Server product and Microsoft team might fix it. If you are lazy and not interested to know the cause, go ahead and delete the files.

They would be generated again, and you need to write a batch file to delete them on a regular basis. If your log folder has several dumps for a few years ago and then no dumps for several months, then a few recent dumps, you can safely delete the old dumps.

Have you found this useful? Please comment and share your experience about the dump. Just turning on the computer, no processing made, SQL dumps error file is automatically created. How to fix this issue? I am a developer and the dumps are the result of mistakes I have made. Can I delete everything there or should I be selective about what files to delete?