Can you lock an entire table in SQL Server while two people are in it and then when one person is in it unlock that entire table?

If someone is editing data belonging to one table and another comes along and starts to edit other data belonging to that same table - what I would like to do is lock it read only for the second user - where he/she cannot change it - sort of what Excel does when two people open the same document - is that possible?    Then if the first user leaves - the locking is removed for the second user - where he/she can change it?

Sure there is a lot online for record-row level locking, column locking would slow performance and then you get into user-permisions.  But this is special to where you want the locking to occur only on the second user (or third, fourth) temporarily and return when there is one user only accessing the table.

Second question - should this not be done at database level but merely only software front-end?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You can lock the entire table for update by using hints.  Something like this:

SELECT Col1, Col2 
   FROM YourTable
    WHERE Col3 in (1, 2, 3);

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
The above will prevent anybody else from reading the table, as the "Intended Update" lock will not allow reads with "Intended Update" locks; else the lost update issue would arise (reading a set of old data, while they are changed by someone else, and then wanting to update those old records). However, it works if you catch the error generated (lock timeout, or deadlock), and then do the same select without the locks. That, however, would require you check the table regularly for being able to lock it again.

A much better approach to lock a complete table is to maintain a control table. As soon as there is an entry for the table to view, you prohibit any update. The first "user" inserts the table with a flag, so you can identify he's the "owner", and able to update. This technique again requires checking, of the control table whenever an update is attempted.
stephenlecomptejrAuthor Commented:
"This technique again requires checking, of the control table whenever an update is attempted."

Is this done as a trigger in SQL server or done within the front-end software accessing sql server?
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Front-End - it is application logic.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.