October 12, 2011 at 7:21 am
Sapen (10/12/2011)
Salom,I was looking into the errorlog file that grew 35GB and all I see is just information messages without any errors and also there were only 26050 records of logs that got pulled up. I still dont understand why that log file grew up to 35GB. All the other errorlogs that I have (ErrorLog.1, Errorlog.2 and so on) are not more than 6 mb.
Thanks for your reply. For how long did the error log run?
October 12, 2011 at 7:48 am
When I executed the Exec Sp_Cycle_Errorlog a new errorlog was created and I was able to open the errorlog based on the timestamp through sql server error log viewer...it took about a couple of seconds to open
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
October 12, 2011 at 8:00 am
Sapen (10/12/2011)
When I executed the Exec Sp_Cycle_Errorlog a new errorlog was created and I was able to open the errorlog based on the timestamp through sql server error log viewer...it took about a couple of seconds to open
Please excuse me for not being able to formulate the question properly. What I want to know is how much data had the 35GB errorlog in terms of days or months? e.g. it ran from May until July. I hope I'm clear enough this time 🙂
October 12, 2011 at 8:08 am
Sapen (10/12/2011)
When I executed the Exec Sp_Cycle_Errorlog a new errorlog was created and I was able to open the errorlog based on the timestamp through sql server error log viewer...it took about a couple of seconds to open
I would expect this to be very small and easy to open with something like textpad since the length of time from the previous log was pretty short (around 24 hours) unless you had something very wrong going on (errors / failed login's..etc)
Ignacio A. Salom Rangel (10/12/2011)
Sapen (10/12/2011)
When I executed the Exec Sp_Cycle_Errorlog a new errorlog was created and I was able to open the errorlog based on the timestamp through sql server error log viewer...it took about a couple of seconds to openPlease excuse me for not being able to formulate the question properly. What I want to know is how much data had the 35GB errorlog in terms of days or months? e.g. it ran from May until July. I hope I'm clear enough this time 🙂
I believe what he is saying here is that in the error log it starts off with the date time that the server service is started, then all the logging that occurs during and after the start up...
what is the date range from when it started to the last date time in that file?
example from one of my test boxes...
2011-09-14 20:23:11.56 Server Microsoft SQL Server 2005 - 9.00.4060.00 (Intel X86)
Mar 17 2011 13:20:38
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2011-09-14 20:23:11.56 Server (c) 2005 Microsoft Corporation.
2011-09-14 20:23:11.56 Server All rights reserved.
2011-09-14 20:23:11.56 Server Server process ID is 1584.
2011-09-14 20:23:11.56 Server Authentication mode is MIXED.
...
...
...
2011-10-12 00:00:11.99 spid17s This instance of SQL Server has been using a process ID of 1584 since 9/14/2011 8:23:15 PM (local) 9/15/2011 1:23:15 AM (UTC). This is an informational message only; no user action is required.
October 12, 2011 at 8:28 am
Leeland (10/12/2011)
Sapen (10/12/2011)
When I executed the Exec Sp_Cycle_Errorlog a new errorlog was created and I was able to open the errorlog based on the timestamp through sql server error log viewer...it took about a couple of seconds to openI would expect this to be very small and easy to open with something like textpad since the length of time from the previous log was pretty short (around 24 hours) unless you had something very wrong going on (errors / failed login's..etc)
Ignacio A. Salom Rangel (10/12/2011)
Sapen (10/12/2011)
When I executed the Exec Sp_Cycle_Errorlog a new errorlog was created and I was able to open the errorlog based on the timestamp through sql server error log viewer...it took about a couple of seconds to openPlease excuse me for not being able to formulate the question properly. What I want to know is how much data had the 35GB errorlog in terms of days or months? e.g. it ran from May until July. I hope I'm clear enough this time 🙂
I believe what he is saying here is that in the error log it starts off with the date time that the server service is started, then all the logging that occurs during and after the start up...
what is the date range from when it started to the last date time in that file?
example from one of my test boxes...
2011-09-14 20:23:11.56 Server Microsoft SQL Server 2005 - 9.00.4060.00 (Intel X86)
Mar 17 2011 13:20:38
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2011-09-14 20:23:11.56 Server (c) 2005 Microsoft Corporation.
2011-09-14 20:23:11.56 Server All rights reserved.
2011-09-14 20:23:11.56 Server Server process ID is 1584.
2011-09-14 20:23:11.56 Server Authentication mode is MIXED.
...
...
...
2011-10-12 00:00:11.99 spid17s This instance of SQL Server has been using a process ID of 1584 since 9/14/2011 8:23:15 PM (local) 9/15/2011 1:23:15 AM (UTC). This is an informational message only; no user action is required.
Thank you! 😉
October 12, 2011 at 8:35 am
Just a PS, that's why Paul Randal's always does a job to cycle the error logs daily and then keep 99 days.
You can more easily spot what and when something went wrong.
October 12, 2011 at 9:03 am
October 12, 2011 at 9:19 am
Ninja's_RGR'us (10/12/2011)
http://www.sqlskills.com/InsiderContent/201108/August2011InsiderTip2.wmv
Thanks! 😉
October 12, 2011 at 9:25 am
You should sign up for his newsletter... great stuff every week.
October 12, 2011 at 9:32 am
Ninja's_RGR'us (10/12/2011)
You should sign up for his newsletter... great stuff every week.
Thanks for the tip!
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply