INF: SQL Server SELECT with HOLDLOCK Transaction Information

 Last reviewed: April 25, 1997
Article ID: Q62859

The information in this article applies to: 

  - Microsoft SQL Server version 4.2 for OS/2

The following information describes what happens when a SELECT is done with HOLDLOCK.

If you do a SELECT with HOLDLOCK within a transaction and get no hits, either an index page or the whole table will be locked until commit.

If the optimizer used a unique index to process the select, the index page where the missing item belongs will be locked. If the optimizer did not use a unique index to process the query, the entire table will be locked.

Additional query words: Transact-SQL
Keywords : kbprg SSrvServer
Version : 4.2 4.2a 4.2b
Platform : OS/2
Issue type : kbtshoot

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.