SSMS Continously Locks up for short periods

  • I'm hpoing this isn't just me. Is anyone else having a problem with SSMS locking up /freezing repeatidly throughout the day even when you aren't running a query? I'm using Vista and I would think it might be because of Vista and its UAC but I did not have this same problem on my prior computer which also used Vista. Thats not to say it's not Vista but that somehow it just never happened on my older Vista box which had half the processing power of my new system.

    I also am using Red Gatres SQL Prompt whcih i used on my old machine too. I also am running both SSMS 2005 & SSMS 2008 but I was doing the same on my old box. Since I have the same items installed & running I can't figure out why I now am having so much trouble.

    The thing will stay frozen for up to 30 seconds before retruning to normal. ANy ideas?

    Kindest Regards,

    Just say No to Facebook!
  • I don't know what it's called in Vista but turn on the equivalent of TaskMgr and see what the cpu and kernal are doing. If the cpu is pegging, select the processes tab and see what's using the cpu time. Credits to Navy Beans says it's the anti-virus software.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Run SQL Profiler to see what SSMS is doing.


    N 56°04'39.16"
    E 12°55'05.25"

  • I get problems occassionally normally down to a sql server process taking too long to complete.

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

  • Jeff Moden (10/5/2009)


    I don't know what it's called in Vista but turn on the equivalent of TaskMgr and see what the cpu and kernal are doing. If the cpu is pegging, select the processes tab and see what's using the cpu time. Credits to Navy Beans says it's the anti-virus software.

    Jeff - I don;t think it's AV software because I did not have this issue on my privous box and I have all the same software installed (its a company box) but I am gonna run TaskMgr now so that next it happens I can switch over quickly and see if anything is peeking the system. I believe I did look at TaskMgr when this first started but since I can't swear to it I'm gonna do it again. I fear this is something specific to Vista and/or Vista with SQL 2005 & 2008 installed but then again I had all 3 of those on my last system.

    The one major diff between this box and the old one is hardware but that is a difference on trhe plus side. The new box is a quad core AMD II X940 Processor @ 3.0 GHZ and the previous box was a DUal core Pentium 2.33 GHz so the new is more powerfull then the old.

    Kindest Regards,

    Just say No to Facebook!
  • Thanks for the feedback. I look forward to what you may find because I can see this becoming more of a problem in the future.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • UPDATE:

    Well yesterday I managed to have TaskMgr open and running when SSMS locked up and while there was no query or other task (like Activity Monitor) running, the process that was draining the memory and CPU was SSMS.exe. I did not have Profiler open either time to trace what was going on but I will make it a point to have it open and ready to trace from now on.

    One interesting side note is that several other things have also changed in the past few days and I have verified with my IT guys that they habe not pushed any changes down to my system. i no longer see the UAC warning when I login &after a reboot) whcih is something I used to see all the time. I checked and it is still showing as being turned on.

    I also noticed that 2 Windows Updates were installed even though I did not do any updates in that time and I have Windows Updates set to download automatically but to let me decide to install. Kind of thinking Microsoft's not being honest on the updates to the OS.

    I just had to do a System Restore to 9/30 (before the first of these 2 Widnows updates I did not autrhorize) because evberything started locking up today, not just SSMS.

    Kindest Regards,

    Just say No to Facebook!
  • UPDATE: The Problem Identified; The Solution Found

    After having to deal with this annoying lockup in SSMS 2008 for many months now I finally happened across the problem and the solution. It's the built-in Auto Recovery feature, soomething you can't change from within SSMS's options. I turned this darn thing off via the Registry and now my woes have gone away. Shame on Microsoft for implementing something like this in a way that requires one to edit the registry to fix it.

    I found the solution at the below URL. I figured out what key words to search on because for the first time since the lockups started I caught a message at the bottom of the SSMS window I normally can't see and the message read :

    Saving Auto Recovery Information

    The URL for the info on this is http://blog-mstechnology.blogspot.com/2009/06/turn-off-saving-auto-recovery.html?showComment=1257369045061#c2793556702063487549

    Kindest Regards,

    Just say No to Facebook!
  • Thank you for the update.


    N 56°04'39.16"
    E 12°55'05.25"

  • Thank you for the update.


    N 56°04'39.16"
    E 12°55'05.25"

Viewing 10 posts - 1 through 9 (of 9 total)

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