Post reply

SQLDump####.mdmp & txt filling C drive on a regular basis

  • April 5, 2011 at 1:06 am

    #248970

    Hi All

    We have an instance of 2005 Standard to which keeps writing mdmp and txt files in the format SQLDump####.mdmp and .txt, these files fill up the C drive on the server periodically.

    While I know we can delete these files without an issue how do we stop them from being created?

    I have deleted around 40GB worth of them this morning as the server had around 6GB free on the C drive, but it is getting to a task which is needed to be done around every two weeks.

    Any help would be appreciated

    Thanks

    Anthony

  • April 5, 2011 at 1:24 am

    #1307320

    I'd be far more worried about the cause than the effect. Those are minidumps, means that SQL is regularly throwing access violations.

    Ensure that SQL is patched to the latest version, if the problem persists, call Microsoft's Customer Support. This could be a very serious problem.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • April 5, 2011 at 1:33 am

    #1307324

    Hi Gail

    Thanks for this, unfortunatly the application which runs is only supported up to SP2 for SQL 2005 as the vendor hasnt got round to testing on their systems for SP3 or SP4.

    I will raise a call with Microsoft to see if they can advise.

    Thanks

    Anthony

  • April 5, 2011 at 1:43 am

    #1307327

    anthony.green (4/5/2011)

    I will raise a call with Microsoft to see if they can advise.

    They'll likely tell you to patch to SP4 and call them back if the problem persists. Maybe take it up with your vendor. SP2 is well out of support these days.

    Access violation = illegal memory access. It's unlikely to be SQL (unless you've encountered a bug), could be anything else though. In process linked server drivers (buggy ones) can have this effect, extended stored procedures can as well. Could be other buggy drivers on the server too.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply