Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Note that you can specify nolock on a per table basis.</p> <p>I typically used nolock in complex SELECT queries, but only for the little lookup tables that almost never changed, and for display-only data. You know the tables that list the prices for the current half year, or lookups of ids to strings etc. Stuff that only changes with major updates after which the servers are usually restarted routinely anyway.</p> <p>This improved performance significantly, reduced the chance of deadlock in the busiest times, and more importantly it was really noticable during the worst case moments for queries that touched a lot of tables (which is logical, they have to obtain less locks, and those sidetables are often used nearly everywhere, often decreasing from 7-8 to 4 tables that need to be locked)</p> <p>But be very careful adding it, don't rush it, and don't do it routinely. It won't hurt when used properly, but it will hurt horribly when used improperly.</p> <p>Don't use it for highly critical stuff, stuff that calculates etc, because it will get inconsistent, anything that leads to a write sooner or later.</p> <p>Another such optimization is ROWLOCK, which only locks on row level. This is mainly useful when updating (or deleting in) tables where the rows are not related to eachother, like tables where you only put in log records (and the order in which they are inserted doesn't matter). If you have a scheme that somewhere in the end of an transaction a log record is written to some table, this can speed up considerably too.</p> <p>If your database has a relatively low percentage writes it might not be worth it. I had a read:write ratio of under 2:1.</p> <p>Some URLs I saved when working on this:</p> <p><a href="http://www.developerfusion.com/article/1688/sql-server-locks/4/" rel="nofollow noreferrer">http://www.developerfusion.com/article/1688/sql-server-locks/4/</a></p>
    singulars
    1. This table or related slice is empty.
    1. POWhen is it appropriate to use NOLOCK?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarco van de Voort
    1. USMarco van de Voort
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CORegarding unfrequently updated tables at read committed level SQL Server can skip taking shared row locks on pages which don't have uncomitted changes anyway. Seems to me `NOLOCK` would give precisely the benefits you mention (faster performance, fewer deadlocks) in the cases where data **is** being updated and you are getting contention.
      singulars
      1. PO
      1. USMartin Smith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload