Crash dump & TMP files in Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps

  • Hi,

    I see so many crash dump and .TMP files in folder Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps (SQL Server 2012 Version).

    No of files are growing more and consuming C drive space fast. Please help on how to get rid of this. Thanks in Advance.

  • Make sure the server is patched to the latest version, and if you're still having stack sumps (which usually indicate fatal errors or severe database corruption), open a case with Micosoft's customer support.

    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
  • This server is running with SP3 (SQL 2012) and it is uptodate. I see the crash dump file names like "ISServer_106368_75a8592f-0076-4e1b-9e4c-0875df46d4f2_0".... and so on. Any idea how it gets created?

  • If they're stack dumps, then they're written out when SQL encounters fatal errors (like invalid memory addresses) or some forms of severe corruption. Either way, repeated stack dumps suggest something is seriously wrong.

    If they are dumps, there will be files .mdmp and .txt at least with the same name. Also there will be messages in the error log stating that SQL stack dumped.

    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