Click here to Skip to main content
15,891,033 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
How to prevent or handle multiple user updatation in same row.?
Posted

 
Share this answer
 
v2
Comments
Ganesh Raja 9-Dec-13 10:03am    
Thanks for the post...:)
Basically the row level lock will happen when we are trying to update and delete the data.But if more then 1 user access to update or delete the data in same time,then how can we handle the situation?[it will queued and will wait for certain time and process the request in db side but the first data updation taking long time then surly next queue data will throw the dead lock error right?]
Is this need to handle in db side or application side?
Vishal Pand3y 9-Dec-13 11:34am    
When you insert/update/delete a row in Sql, sql will lock the table/row/page to guarantee that you will be able to do what you want. This lock will be released when you are done inserting/updating/deleting the row.
This is called concurrency issue. look at the article to understand.

http://blog.sqlauthority.com/2012/11/15/sql-server-concurrency-basics-guest-post-by-vinod-kumar/[^]
 
Share this answer
 
Comments
Ganesh Raja 9-Dec-13 10:04am    
Thanks for the post...:)
Basically the row level lock will happen when we are trying to update and delete the data.But if more then 1 user access to update or delete the data in same time,then how can we handle the situation?[it will queued and will wait for certain time and process the request in db side but the first data updation taking long time then surly next queue data will throw the dead lock error right?]
Is this need to handle in db side or application side?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900