Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

MSSQL logs eating disk space Expand / Collapse
Author
Message
Posted Wednesday, March 19, 2014 12:31 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, March 20, 2014 9:40 AM
Points: 1, Visits: 9
Hi Guys,

We are having an issue with MSSQL logs (C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\) eating disk space after making a backup restore of the server. Logs were eating up to 10 Gb of space in just a day.

server crestes SQLDumpxxxx.log,SQLDumpxxxx.mdmp and SQLDumpxxxx.txt> Tried deleting it but it keeps generating logs.




2014-02-15 22:26:37.55 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 6.0 (Build 6002: Service Pack 2)

2014-02-15 22:26:37.57 Server (c) 2005 Microsoft Corporation.
2014-02-15 22:26:37.57 Server All rights reserved.
2014-02-15 22:26:37.57 Server Server process ID is 11764.
2014-02-15 22:26:37.57 Server Authentication mode is WINDOWS-ONLY.
2014-02-15 22:26:37.57 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2014-02-15 22:26:37.57 Server This instance of SQL Server last reported using a process ID of 3004 at 2/15/2014 10:19:40 PM (local) 2/16/2014 6:19:40 AM (UTC). This is an informational message only; no user action is required.
2014-02-15 22:26:37.57 Server Registry startup parameters:
2014-02-15 22:26:37.57 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2014-02-15 22:26:37.57 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2014-02-15 22:26:37.57 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2014-02-15 22:26:37.60 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-02-15 22:26:37.60 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-02-15 22:26:38.14 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-02-15 22:26:38.49 Server Database mirroring has been enabled on this instance of SQL Server.
2014-02-15 22:26:38.53 spid5s Starting up database 'master'.
2014-02-15 22:26:38.74 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-02-15 22:26:39.08 spid5s SQL Trace ID 1 was started by login "sa".
2014-02-15 22:26:39.11 spid5s Starting up database 'mssqlsystemresource'.
2014-02-15 22:26:39.13 spid5s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2014-02-15 22:26:39.52 spid8s Starting up database 'model'.
2014-02-15 22:26:39.55 spid5s Server name is 'CORP\SBSMONITORING'. This is an informational message only. No user action is required.
2014-02-15 22:26:39.75 Server The certificate was successfully loaded for encryption.
2014-02-15 22:26:39.77 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SBSMONITORING ].
2014-02-15 22:26:39.77 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SBSMONITORING\sql\query ].
2014-02-15 22:26:39.77 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2014-02-15 22:26:39.78 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-02-15 22:26:39.95 spid8s Clearing tempdb database.
2014-02-15 22:26:39.97 spid5s Starting up database 'msdb'.
2014-02-15 22:26:41.37 spid8s Starting up database 'tempdb'.
2014-02-15 22:26:41.78 spid5s Recovery is complete. This is an informational message only. No user action is required.
2014-02-15 22:26:41.79 spid11s The Service Broker protocol transport is disabled or not configured.
2014-02-15 22:26:41.79 spid11s The Database Mirroring protocol transport is disabled or not configured.
2014-02-15 22:26:41.89 spid11s Service Broker manager has started.
2014-02-15 22:30:00.20 Server Server resumed execution after being idle 166 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2014-02-15 22:30:00.43 spid51 Starting up database 'SBSMonitoring'.
2014-02-15 22:30:01.55 spid51 Recovery is writing a checkpoint in database 'SBSMonitoring' (5). This is an informational message only. No user action is required.
2014-02-15 22:32:41.27 spid51 ex_raise2: Exception raised, major=52, minor=43, state=1, severity=22, attempting to create symptom dump
2014-02-15 22:32:41.28 spid51 Using 'dbghelp.dll' version '4.0.5'
2014-02-15 22:32:41.28 spid51 **Dump thread - spid = 51, PSS = 0x804ED540, EC = 0x804ED548
2014-02-15 22:32:41.28 spid51 *
2014-02-15 22:32:41.28 spid51 * User initiated stack dump. This is not a server exception dump.
2014-02-15 22:32:41.28 spid51 *
2014-02-15 22:32:41.28 spid51 ***Stack Dump being sent to C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
2014-02-15 22:32:41.28 spid51 * *******************************************************************************
2014-02-15 22:32:41.28 spid51 *
2014-02-15 22:32:41.28 spid51 * BEGIN STACK DUMP:
2014-02-15 22:32:41.28 spid51 * 02/15/14 22:32:41 spid 51
2014-02-15 22:32:41.28 spid51 *
2014-02-15 22:32:41.28 spid51 * ex_raise2: Exception raised, major=52, minor=43, state=1, severity=22


Also, just recently we have noticed that disabling the SBS$MONITORING stop it from generating logs. Any idea how is it related, or what could be the issue.

Any advise is greatly appreciated.

Thank you,

jace
Post #1552761
Posted Wednesday, March 19, 2014 2:11 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:13 PM
Points: 39,866, Visits: 36,208
Something's throwing high severity errors and SQL is writing out stack dumps to log information which may help identify and fix the problem (severity 22 are severe errors which need to be addressed as a matter of urgency). Either investigate the cause of the errors yourself or open a case with Microsoft support and get their help. The main concern here is not the large log directory, it's those severity 22 errors (the highest possible severity is 25)


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1552790
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse