April 28, 2011 at 2:05 pm
Hey all,
I am writing to confirm the possibility of a bug within SQL in regards to the error logs. I've never noticed this before, but while writing a new object to determine outage duration based on restarts, I've come to notice an oddity within my data.
In SSMS, either running EXEC [master].[dbo].[xp_enumerrorlogs] or under management -> SQL Server Logs, you'll see the listing of all your error logs with a time stamp. This time stamp, is the last time that particular error log was written to.
Now, compare that time stamp to the last entry in the error log for a month like February. For me, in all environments both 2005 and 2008, the timestamp from enumerrorlogs is one hour ahead of the last entry in the error log.
I'm going to put something up on connect about this but wanted to ensure that I'm not overlooking anything here.
Also, any recommendations on resolution here? Do I utilize like a daylight savings time function? Can't say this is ever an issue I've had to deal with.
Thanks all
April 28, 2011 at 2:31 pm
Well considering that is an undocumented stored procedure I doubt you are going to get much help by putting a Connect item out there.
I checked a SQL Server 2005 instance I have and it is showing the same timestamp. Are your instances at the most current service pack level?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 28, 2011 at 2:36 pm
Shawn Melton (4/28/2011)
Well considering that is an undocumented stored procedure I doubt you are going to get much help by putting a Connect item out there.I checked a SQL Server 2005 instance I have and it is showing the same timestamp. Are your instances at the most current service pack level?
Yeah I thought the same as well in regards to support. I just wonder if it's ever been brought to their attention is all.
Yes, I'm seeing this on all product levels of SQL2000, 2005, 2008 and R2 on an environment with about 250 instances.
Did you check the different months? More specifically, months between November and March?
I found a lame short term work around that resolves my issue for the time being; however I just thought this issue was interesting and wanted to see if others are seeing the same.
April 28, 2011 at 2:51 pm
Adam Bean (4/28/2011)Did you check the different months? More specifically, months between November and March?
We cycle the error logs in SQL frequently so I don't show logs back to Nov in SSMS on most instances.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 28, 2011 at 2:53 pm
Shawn Melton (4/28/2011)
Adam Bean (4/28/2011)Did you check the different months? More specifically, months between November and March?
We cycle the error logs in SQL frequently so I don't show logs back to Nov in SSMS on most instances.
Understandable, as do we; however we usually keep 12 logs.
Just trying to confirm that this is an issue seen in other environments or not as I'm assuming that it is.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply