Post reply

SQL Server 2005 Crash

  • February 3, 2010 at 6:12 am

    #138569

    Hi All

    Was wondering if anyone can shed some light on the attached error logs.

    Users were reporting that the applications were timing out. On the breif moment that our server desk could get onto the server they could only see that the CPU was high (98%) and memory was @ about 80% usage.

    This is a SQL 2005 SP3 x86, 16Gb Ram and 2.3Ghz quadh proc.

    After rebooting the server all seems to be ok

  • February 4, 2010 at 2:15 am

    #1113551

    Could be related to http://support.microsoft.com/kb/973524 ?

    As googling for 'usp_DeadlockNotification' revealed this proc which executes xp_readerrorlog. Is that the same as your 'usp_DeadlockNotification' ?


    Clear Sky SQL
    My Blog[/url]

  • February 4, 2010 at 2:35 am

    #1113565

    Dave

    Thanks for the reply...

    I current am running 9.00.4226, which is SP3 CU6. According to my monitoring tools the server was maxing CPU before the 0900 job for deadlock notification kick off (think this was the final screw!!).

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

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