INF: Support of Page and Table Locking in SQL Server

Last reviewed: April 25, 1997
Article ID: Q46170

The information in this article applies to:

  - Microsoft SQL Server version 4.2 for OS/2

SQL Server will lock only the page containing the updated row if an index was used to locate that row. If an index was not used to locate the row, by (for example) using the sp_lock() function, the entire table will be locked.

Using NOT in a WHERE clause or creating an index before data is loaded and not UPDATING STATISTICS can cause SQL Server to not use indexes.

If a non-clustered index is used to locate a row, the data page will be locked as well as the leaf-level index page used to locate the row, even if the value of the indexed column is not changed. If the row was located via clustered index, only the data page will be locked (unless the values of indexed columns are changed).

Additional query words:
Keywords : kbprg SSrvServer
Version : 4.2
Platform : OS/2

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.