Post reply

SQL server log folder

  • March 19, 2014 at 7:40 am

    #284751

    My SQL server log folder is filling up so fast what could be causing this?The path is C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log

    and the file names are SQLDUMP extensions .txt and .mdmp.

    “When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

  • March 19, 2014 at 7:56 am

    #1698379

    You're having stack dumps, severe exceptions which result in SQL writing out diagnostic information. Rather than worry about the space, maybe worry about why you're having a lot of very severe errors.

    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

  • March 19, 2014 at 9:03 am

    #1698409

    Event 7105:MSSQLSERVER:The Database ID 7, Page (1:144949), slot 6 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE.

    I executed database integrity check but issue still occurs.

    “When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

  • March 19, 2014 at 9:06 am

    #1698412

    You appear to have a corrupt database. Got any clean backups?

    When did you last successfully run DBCC CheckDB?

    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

  • March 20, 2014 at 1:15 am

    #1698579

    I have identified a corrupt database and DBCC CHECKDB is failing.

    “When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

  • March 20, 2014 at 2:34 am

    #1698588

    Good, so you know the cause of the problem then. Fixing the corrupt DB will stop the stack dumps. Good luck.

    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 6 posts - 1 through 5 (of 5 total)

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