In order to provide any significant advice, we need to know how your application works. At what point do you want to lock rows? When the data is read? When the user does an update?
In my opinion, most applications should allow SQL Server to handle locking. I certainly advise against using tablock. That can make a system nearly unusable in a multi-user environment.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.