sql server - multiple queries running at the same time WITH(NOLOCK) -


considering highly active remote database in constant use; 2 or perhaps more concurrently running queries returning around 30m records using with(nolock) in query make system unusable?

highly active: around 200 users varying queries ranging 1 record queries maximum above.

constant: 18/7

unusable: 5-15 minute delays. external apps or users not being able reach db query.

you need investigate downtime 'unusable' appropiate. guessing not work. there many situations can make server 'unusable', like:

  • database growth
  • log growth
  • core dump
  • scheduler exhaustion
  • many more

other times server can 'slow' , appear unresponsive. 200 queries scanning nilly-willy 30 million rows table can lead scheduler exhaustion. need investigate. waits , queues methodology use (for instance correctly identify scheduler exhaustion mentioned above).

as nolock: there never valid reason use nolock. users see incorrect data right now. consider using row versioning instead.


Comments

Popular posts from this blog

Change php variable from jquery value using ajax (same page) -

Pull out data related to my apps from Android Play Store and iOS App Store -

How can I fetch data from a web server in an android application? -