June 20, 2013 at 6:10 am
Hi all,
when i checked my error log it has taken 100 gb of space and my disk is out of space. when i checked log folder location i found so many sqldump mdmp files. i am not sure whats going on... i deleted all those files and started sql server.. but i can see they are still generating mdmp files and falling in to the log folder.
June 20, 2013 at 6:42 am
Is it possible to attach a screen shot of the folder(set the view to details so that we can see the name,date modified, type, size
and also the path/location where your looking at these files.
June 20, 2013 at 6:47 am
here is the error log
2013-06-20 17:33:47.470ServerMicrosoft SQL Server 2008 R2 (SP1) - 10.50.2796.0 (X64) Dec 9 2011 11:27:20 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2013-06-20 17:33:47.470Server(c) Microsoft Corporation.
2013-06-20 17:33:47.470ServerAll rights reserved.
2013-06-20 17:33:47.470ServerServer process ID is 3220.
2013-06-20 17:33:47.470ServerSystem Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 330'.
2013-06-20 17:33:47.470ServerAuthentication mode is MIXED.
2013-06-20 17:33:47.490ServerLogging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-06-20 17:33:47.500ServerThis instance of SQL Server last reported using a process ID of 1140 at 6/20/2013 5:32:05 PM (local) 6/20/2013 12:02:05 PM (UTC). This is an informational message only; no user action is required.
2013-06-20 17:33:47.500ServerRegistry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2013-06-20 17:33:47.540ServerSQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-06-20 17:33:47.540ServerDetected 2 CPUs. This is an informational message; no user action is required.
2013-06-20 17:33:47.630ServerUsing locked pages for buffer pool.
2013-06-20 17:33:47.850ServerUsing 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.
2013-06-20 17:33:48.310ServerNode configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-20 17:33:48.430spid7sStarting up database 'master'.
2013-06-20 17:33:48.690spid7sRecovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-06-20 17:33:49.040spid7sResource governor reconfiguration succeeded.
2013-06-20 17:33:49.060spid7sSQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-06-20 17:33:49.060spid7sSQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-06-20 17:33:49.080spid7sFILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-06-20 17:33:49.210spid7sSQL Trace ID 1 was started by login "sa".
2013-06-20 17:33:49.230spid7sStarting up database 'mssqlsystemresource'.
2013-06-20 17:33:49.250spid7sThe resource database build version is 10.50.2796. This is an informational message only. No user action is required.
2013-06-20 17:33:49.550spid10sStarting up database 'model'.
2013-06-20 17:33:49.610spid7sServer name is 'QBSNEWSVR'. This is an informational message only. No user action is required.
2013-06-20 17:33:50.290spid10sClearing tempdb database.
2013-06-20 17:33:50.850ServerThe certificate [Cert Hash(sha1) "1667465C3D9F7AA06A8E4A71C829C12C8D495B3B"] was successfully loaded for encryption.
2013-06-20 17:33:51.020ServerServer is listening on [ 'any' <ipv6> 1433].
2013-06-20 17:33:51.030ServerServer is listening on [ 'any' <ipv4> 1433].
2013-06-20 17:33:51.030ServerServer local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2013-06-20 17:33:51.030ServerServer local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2013-06-20 17:33:51.030ServerServer is listening on [ ::1 <ipv6> 1434].
2013-06-20 17:33:51.030ServerServer is listening on [ 127.0.0.1 <ipv4> 1434].
2013-06-20 17:33:51.030ServerDedicated admin connection support was established for listening locally on port 1434.
2013-06-20 17:33:51.200LogonError: 17187, Severity: 16, State: 1.
2013-06-20 17:33:51.200LogonSQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: 192.168.1.163]
2013-06-20 17:33:51.230LogonError: 17187, Severity: 16, State: 1.
2013-06-20 17:33:51.230LogonSQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: ::1]
2013-06-20 17:33:51.230LogonError: 17187, Severity: 16, State: 1.
2013-06-20 17:33:51.230LogonSQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: 192.168.1.163]
2013-06-20 17:33:51.270ServerThe SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/qbsnewsvr.QBSTRUST.COM ] for the SQL Server service.
2013-06-20 17:33:51.270ServerThe SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/qbsnewsvr.QBSTRUST.COM:1433 ] for the SQL Server service.
2013-06-20 17:33:51.270ServerSQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-06-20 17:33:52.630spid13sA new instance of the full-text filter daemon host process has been successfully started.
2013-06-20 17:33:52.770spid10sStarting up database 'tempdb'.
2013-06-20 17:33:52.980spid13sStarting up database 'msdb'.
2013-06-20 17:33:52.980spid14sStarting up database 'IncuityStore'.
2013-06-20 17:33:52.980spid15sStarting up database 'IncuitySample'.
2013-06-20 17:33:52.990spid16sStarting up database 'IncuityHistory'.
2013-06-20 17:33:53.010spid17sStarting up database 'IncuityDiagnostics'.
2013-06-20 17:33:53.010spid18sStarting up database 'Tfs_Configuration_Old'.
2013-06-20 17:33:53.010spid19sStarting up database 'Tfs_Rockwell IPE Tool'.
2013-06-20 17:33:53.010spid20sStarting up database 'Tfs_Rockwell IPE Tool Phase0'.
2013-06-20 17:33:53.710spid21sThe Service Broker protocol transport is disabled or not configured.
2013-06-20 17:33:53.710spid21sServer is listening on [ 'any' <ipv6> 5022].
2013-06-20 17:33:53.710spid21sServer is listening on [ 'any' <ipv4> 5022].
2013-06-20 17:33:53.710spid21sThe Database Mirroring protocol transport is now listening for connections.
2013-06-20 17:33:54.560spid21sService Broker manager has started.
2013-06-20 17:33:57.610spid16sStarting up database 'Tfs_Rockwell IPE Tool Phase2'.
2013-06-20 17:33:57.970LogonError: 18456, Severity: 14, State: 38.
2013-06-20 17:33:57.970LogonLogin failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:33:57.970LogonError: 18456, Severity: 14, State: 38.
2013-06-20 17:33:57.970LogonLogin failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:33:57.970spid17sStarting up database 'IPE_MASTER'.
2013-06-20 17:33:57.970spid15sStarting up database 'IPE_QUOTE'.
2013-06-20 17:34:00.530spid7sRecovery completed for database IPE_QUOTE (database ID 14) in 1 second(s) (analysis 322 ms, redo 0 ms, undo 319 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:01.680spid7sRecovery completed for database Tfs_Rockwell IPE Tool (database ID 10) in 1 second(s) (analysis 329 ms, redo 0 ms, undo 322 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:02.620spid15sRecovery completed for database Tfs_Configuration_Old (database ID 9) in 1 second(s) (analysis 329 ms, redo 0 ms, undo 248 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:02.630spid15sStarting up database 'IPE_QUOTE_OCT_17'.
2013-06-20 17:34:03.350spid7sRecovery completed for database IncuityStore (database ID 5) in 1 second(s) (analysis 321 ms, redo 0 ms, undo 359 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:04.840spid18sStarting up database 'IPE_MASTER_OCT_17'.
2013-06-20 17:34:05.860spid14sRecovery completed for database IPE_QUOTE_OCT_17 (database ID 15) in 1 second(s) (analysis 644 ms, redo 0 ms, undo 310 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:05.860spid14sStarting up database 'Tfs_SilverlightProjects'.
2013-06-20 17:34:06.670spid19sStarting up database 'RhythemSociety'.
2013-06-20 17:34:07.550spid15sStarting up database 'Tfs_SilverlightProjects1'.
2013-06-20 17:34:08.060LogonError: 18456, Severity: 14, State: 38.
2013-06-20 17:34:08.060LogonLogin failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:08.060LogonError: 18456, Severity: 14, State: 38.
2013-06-20 17:34:08.060LogonLogin failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:08.630spid7sRecovery completed for database msdb (database ID 4) in 1 second(s) (analysis 303 ms, redo 0 ms, undo 397 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:11.060spid13sStarting up database 'IPE_MASTER_MAR_22'.
2013-06-20 17:34:13.280spid51Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2013-06-20 17:34:13.280spid51FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-06-20 17:34:13.710spid7sRecovery completed for database Tfs_Rockwell IPE Tool Phase0 (database ID 11) in 1 second(s) (analysis 774 ms, redo 0 ms, undo 397 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:13.810spid7sRecovery completed for database RhythemSociety (database ID 18) in 1 second(s) (analysis 464 ms, redo 0 ms, undo 485 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:15.950spid19sStarting up database 'IPE_QUOTE_MAR_22'.
2013-06-20 17:34:16.340spid7sRecovery completed for database Tfs_SilverlightProjects1 (database ID 19) in 1 second(s) (analysis 260 ms, redo 0 ms, undo 375 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:18.950spid20sRecovery completed for database IPE_QUOTE_MAR_22 (database ID 21) in 1 second(s) (analysis 309 ms, redo 0 ms, undo 155 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:18.950spid20sStarting up database 'Test'.
2013-06-20 17:34:19.390spid7sRecovery completed for database Tfs_Rockwell IPE Tool Phase2 (database ID 12) in 1 second(s) (analysis 291 ms, redo 0 ms, undo 296 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:20.080spid14sStarting up database 'Tfs_Configuration'.
2013-06-20 17:34:21.190spid15sStarting up database 'Tfs_Silverlight'.
2013-06-20 17:34:21.550spid51Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2013-06-20 17:34:21.550spid51Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2013-06-20 17:34:21.980spid19sStarting up database 'Tfs_DotNetProjects'.
2013-06-20 17:34:23.950spid7sRecovery completed for database Test (database ID 23) in 1 second(s) (analysis 446 ms, redo 0 ms, undo 344 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:24.610spid16sStarting up database 'IPE_QUOTE_MAY_31'.
2013-06-20 17:34:27.340spid20sStarting up database 'IPE_QUOTE_OCT_1'.
2013-06-20 17:34:27.680spid51Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2013-06-20 17:34:27.750spid51Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2013-06-20 17:34:29.770spid51Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2013-06-20 17:34:30.050spid51Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2013-06-20 17:34:30.400LogonError: 18456, Severity: 14, State: 38.
2013-06-20 17:34:30.400LogonLogin failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:30.400LogonError: 18456, Severity: 14, State: 38.
2013-06-20 17:34:30.400LogonLogin failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:31.220spid7sRecovery completed for database Tfs_DotNetProjects (database ID 29) in 1 second(s) (analysis 277 ms, redo 0 ms, undo 862 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:31.890spid7sRecovery completed for database IPE_QUOTE_MAY_31 (database ID 31) in 1 second(s) (analysis 596 ms, redo 0 ms, undo 355 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:32.740spid7sRecovery is writing a checkpoint in database 'Tfs_Configuration' (27). This is an informational message only. No user action is required.
2013-06-20 17:34:32.740spid7sRecovery completed for database Tfs_Configuration (database ID 27) in 1 second(s) (analysis 327 ms, redo 220 ms, undo 63 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:34.250spid16sStarting up database 'IPE_QUOTE_20130613'.
2013-06-20 17:34:34.370spid14sStarting up database 'KovaiCRM_1'.
2013-06-20 17:34:35.710spid7sRecovery completed for database IPE_MASTER_MAR_22 (database ID 20) in 1 second(s) (analysis 353 ms, redo 0 ms, undo 351 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:37.020spid7sRecovery completed for database IPE_MASTER_OCT_17 (database ID 16) in 1 second(s) (analysis 423 ms, redo 0 ms, undo 485 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:37.580spid18sCHECKDB for database 'IPE_MASTER_OCT_17' finished without errors on 2013-05-15 10:32:37.900 (local time). This is an informational message only; no user action is required.
2013-06-20 17:34:37.640spid7sRecovery completed for database KovaiCRM_1 (database ID 34) in 1 second(s) (analysis 723 ms, redo 0 ms, undo 488 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:38.550spid7sRecovery completed for database IPE_MASTER (database ID 13) in 1 second(s) (analysis 215 ms, redo 0 ms, undo 286 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:42.480spid7sRecovery is writing a checkpoint in database 'IPE_QUOTE_20130613' (33). This is an informational message only. No user action is required.
2013-06-20 17:34:42.480spid7sRecovery completed for database IPE_QUOTE_20130613 (database ID 33) in 1 second(s) (analysis 348 ms, redo 333 ms, undo 95 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:43.760spid7sRecovery is writing a checkpoint in database 'Tfs_Silverlight' (28). This is an informational message only. No user action is required.
2013-06-20 17:34:43.760spid7sRecovery completed for database Tfs_Silverlight (database ID 28) in 1 second(s) (analysis 195 ms, redo 256 ms, undo 18 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:49.360spid7sRecovery is complete. This is an informational message only. No user action is required.
2013-06-20 17:34:54.870spid17sex_raise2: Exception raised, major=52, minor=42, state=9, severity=22, attempting to create symptom dump
2013-06-20 17:34:54.870spid17sUsing 'dbghelp.dll' version '4.0.5'
2013-06-20 17:34:54.870spid17s**Dump thread - spid = 0, EC = 0x0000000082596B20
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s* User initiated stack dump. This is not a server exception dump.
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt
2013-06-20 17:34:54.870spid17s* *******************************************************************************
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s* BEGIN STACK DUMP:
2013-06-20 17:34:54.870spid17s* 06/20/13 17:34:54 spid 17
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s* ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s*
2013-06-20 17:34:54.870spid17s* MODULE BASE END SIZE
2013-06-20 17:34:54.870spid17s* sqlservr 0000000000D60000 0000000004944FFF 03be5000
2013-06-20 17:34:54.870spid17s* ntdll 00000000776C0000 0000000077868FFF 001a9000
2013-06-20 17:34:54.870spid17s* kernel32 00000000775A0000 00000000776BEFFF 0011f000
2013-06-20 17:34:54.870spid17s* KERNELBASE 000007FEFD550000 000007FEFD5BAFFF 0006b000
2013-06-20 17:34:54.870spid17s* ADVAPI32 000007FEFEAD0000 000007FEFEBAAFFF 000db000
2013-06-20 17:34:54.870spid17s* msvcrt 000007FEFEEA0000 000007FEFEF3EFFF 0009f000
2013-06-20 17:34:54.870spid17s* sechost 000007FEFD910000 000007FEFD92EFFF 0001f000
2013-06-20 17:34:54.870spid17s* RPCRT4 000007FEFF3F0000 000007FEFF51CFFF 0012d000
2013-06-20 17:34:54.870spid17s* MSVCR80 00000000751F0000 00000000752B8FFF 000c9000
2013-06-20 17:34:54.870spid17s* MSVCP80 00000000740C0000 00000000741C8FFF 00109000
2013-06-20 17:34:54.870spid17s* sqlos 0000000073EF0000 0000000073EF6FFF 00007000
2013-06-20 17:34:54.870spid17s* Secur32 000007FEFD130000 000007FEFD13AFFF 0000b000
2013-06-20 17:34:54.870spid17s* SSPICLI
June 20, 2013 at 6:54 am
one of the dump file information due to space constrait only top portion of dump is pasted. i dont know how to attach a file to this forum
Current time is 18:22:48 06/20/13.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.50.2796.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz.
Bios Version is DELL - 15
Phoenix ROM BIOS PLUS Version 1.10 A03
2 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.
Memory
MemoryLoad = 92%
Total Physical = 2036 MB
Available Physical = 161 MB
Total Page File = 4073 MB
Available Page File = 1284 MB
Total Virtual = 8388607 MB
Available Virtual = 8386208 MB
**Dump thread - spid = 0, EC = 0x0000000094D6CB20
*
* User initiated stack dump. This is not a server exception dump.
*
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0288.tx
t
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 06/20/13 18:22:48 spid 16
*
* ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22
*
*
*
* MODULE BASE END SIZE
* sqlservr 0000000000D60000 0000000004944FFF 03be5000
* ntdll 00000000776C0000 0000000077868FFF 001a9000
* kernel32 00000000775A0000 00000000776BEFFF 0011f000
* KERNELBASE 000007FEFD550000 000007FEFD5BAFFF 0006b000
* ADVAPI32 000007FEFEAD0000 000007FEFEBAAFFF 000db000
June 20, 2013 at 7:31 am
in event viewer
administrative event it is showing
An error occurred while writing a trace event to the file, \\?\C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log\FlightRecorderCurrent.trc.
An error occurred while closing the trace output file, \\?\C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log\FlightRecorderCurrent.trc.
June 20, 2013 at 7:56 am
Call Product Support and open a case, you're getting SQL dumping stack dumps, this is potentially a severe 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
June 20, 2013 at 7:33 pm
Hi,
I am planning to migrate from this server to another does this solve this issue ...
June 21, 2013 at 12:41 am
Maybe, maybe not. Depends on what the root cause is.
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
June 21, 2013 at 4:30 am
why don’t you recycle SQL error log by exec sp_cycle_errorlog.
SQL will recycle the log and the physical log file will be inactive (it can be deleted).
my recommendation would be .....recycle the error log.....delete the old files (so that you can have free space back on disk)
now monitor if the error log is still growing. if so that go through the logs and see what causing it to grow. Hopefully it should be fine after recycle.
June 21, 2013 at 4:35 am
DKG-967908 (6/21/2013)
why don’t you recycle SQL error log by exec sp_cycle_errorlog.
It's not that his error log is growing, it's that SQL is stack dumping and writing large stack dumps into the error log directory. The running out of space is a symptom, the problem is that SQL is stack dumping.
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
June 21, 2013 at 5:19 am
The issue has been resolved by dropping the corrupted database.
Thanks Gail for your support
June 21, 2013 at 5:22 am
The problem is solved by dropping corrupted database.
Thanks for every one for your support.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply