June 25, 2014 at 8:44 am
I understand SQL locking ,the different types and when they are used.
But, If a user was to open a table in management studio for editing, does this place a lock on the table (maybe a shared lock) and would it cause any issues if other transaction needed to run an update\insert\delete on the table, such as an overnight import.
June 25, 2014 at 8:55 am
SQLSteve (6/25/2014)
I understand SQL locking ,the different types and when they are used.But, If a user was to open a table in management studio for editing, does this place a lock on the table (maybe a shared lock) and would it cause any issues if other transaction needed to run an update\insert\delete on the table, such as an overnight import.
1) Test this yourself and see what happens. Do it on a test system where you are only one connected and then run sp_lock or sp_whoisactive with the appropriate parameter set.
2) I would personally never use SSMS to edit data (or schema or lots of other stuff)!! It is very buggy!
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply