Post reply

Event time from deadlock in system_health different from time in error log

  • March 7, 2013 at 9:44 am

    #269387

    Can anyone explain why I would have an event time of 2013-03-07 05:39:21.027 for a deadlock in the ring buffer, but when I look at the event in the SQL Error Log (we have flag 1222 on) it shows a time of 2013-03-06 11:39:30 PM. This is quite a time difference and I thought the ring buffer was synchronous. Any thoughts?

    Jared
    CE - Microsoft

  • March 7, 2013 at 9:57 am

    #1594547

    There is a bug - see link

    http://www.sqlskills.com/blogs/jonathan/incorrect-timestamp-on-events-in-extended-events/[/url]


    Check Your SQL Servers Quickly and Easily
    www.sqlcopilot.com

  • March 7, 2013 at 10:05 am

    #1594558

    Yes, but I do have 2008 R2 SP1 CU on all servers. Is it possible that this is reading GMT time and not system time? We are CST and this is remarkably close to 6 hours. I suppose I can research this now that I have something to go on.

    Jared
    CE - Microsoft

  • March 7, 2013 at 10:09 am

    #1594564

    Aha, yes you've hit the nail on the head. Extended events report GMT.

    Living in the UK I only have to account for that during the summer 🙂


    Check Your SQL Servers Quickly and Easily
    www.sqlcopilot.com

Viewing 4 posts - 1 through 3 (of 3 total)

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