I have some databases with corrupt mdf and my C dive on the SQL server is getting maxed out with error dump files,

I am not asking how to troubleshoot why these files are being created, I already know what the problem is, why they are being created and what I need to do to correct the underlying issue.

what I would like to know is how to prevent or limit the creation and retention of these dump files so they don't max out my C drive while I am doing repairs


  • If you are not planning to use the dump files, schedule a PowerShell script to delete them. Or you could try the suggestion I made in your other question about this.
    – Dan Guzman
    Commented Jul 18, 2015 at 22:03

1 Answer 1


You should limit your error log size. According to support, you can accomplish this by executing on the target instance the following script:

USE [master];

EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE',
    N'ErrorLogSizeInKb', REG_DWORD, 5120;

Another thing you might want to check is where you have your TempDB stored. If it's on C drive, than perhaps you should move it to another drive.

If you'te getting memory minidumps due to crashes of the database engine, than you should follow Dan Guzman's suggestion and create a script to move or delete them.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.