Could having SSMS open for long periods of time, cause locking?

  • About an hour or so ago I had all of my users come to me, complaining that their application had locked up. Now, for me all of my users is a small number, especially compared to many of you. However for us it's a big deal. So I frantically went about to their machines (we don't have anything like desk support, so we've got to do that as well as wear a dozen other hats). By the time I got back to my machine I believe the situation had resolved itself.

    But one thing I'm wondering about, could having SSMS open cause a locking connection? I doubt it, but I want to double check. I had run a couple of queries earlier in the day, and just left SSMS open. It was doing anything, but I just wonder.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • If you were performing index maintenance it could be briefly possible, or if you were running a query within a transaction, it would have blocked any other user/process accessing your record(s)/table(s) until it was committed or rolled back.

    If you were just running SELECT statements, I don't see any reason it would block anything at a sever-level

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • SSMS by itself doesn't cause any locking. It's the queries through SSMS that causes locking\ blocking. Basically its a long running open transaction that can cause issues. Next time when you notice blocking, check the application that's causing it.

    --SQLBuddy

  • I've never seen SSMS by itself cause any issues and I've left it open for days at a time.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • I guess it depends on when you say you have Mgt Studio open... are you just connected or did you have an open query or something?

    I know if you 'design' a table and leave it that way to do have a type of schema lock that will cause some blocking...

  • No, SSMS open won't create any locking/blocking but I guess as you have mention that you opened SSMS and executed a few queries and if it ran for longer duration may cause the blocking.

    However next time you can use Activity monitor to find out if is there any issue?

    HTH

    ---------------------------------------------------
    "Thare are only 10 types of people in the world:
    Those who understand binary, and those who don't."

  • Markus (4/1/2014)


    I guess it depends on when you say you have Mgt Studio open... are you just connected or did you have an open query or something?

    I know if you 'design' a table and leave it that way to do have a type of schema lock that will cause some blocking...

    I had SSMS open. I did run some SELECT statements, but that was it. It was just open, sitting there.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • That 'can' hold some share locks... if there are heavily updated rows that are attempting to happen as you have an open query to the data there could be some blocking/locking, depending on your isolation level on the db.

  • No, so...

    Step 1. Install sp_WhoIsActive for next time

    Step 2. Profit

  • I've never heard of sp_WhoIsActive. I've done a quick search and found some information on it. I've downloaded it, too, but WOW, is the stored procedure big!

    Kindest Regards, Rod Connect with me on LinkedIn.

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

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