In addition, generally speaking, 1000 user accesses per minute can be easily
handled by SQL Server in a decent hardware environment, and there is no need
to resort to NO LOCK. Of course, you don't have to try very hard to design a
system that can choke up with only a few users.
Linchi
"Rogers" wrote:
Quote:
I am looking for expert advice regarding the simultaneous access one of our
production database.
In my database I have insert, update and select stored procedure and we have
registration database like people access that database simultaneously like
1000 users in 1 minute. We have one module called insert/update users and
other module is search. I am thinking in search stored procedure if I used
NOLOCK locking hint, this will solve my problem of searching, can anyone give
me expert advice on it.
Thanks |