The information in this article applies to:
BUG# NT: 908 (4.2) SYMPTOMSWhen performing an update-in-place on a table with the row size padded out to one row per page, Microsoft SQL Server obtains an update_page lock on two different pages - one on the page actually being updated and the other on the next page in the page chain. The second page is never actually written to, but the update_page lock is held until the transaction is complete. This scenario is commonly used to create a sequence number table to generate row sequence numbers. WORKAROUND
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. This problem was corrected in SQL Server version 6.0. For more information, contact your primary support provider. MORE INFORMATION
The sp_lock output in the following script illustrates the problem:
Additional query words: sql6 Windows NT
Keywords : kbprg SSrvLock SSrvTran_SQL kbbug4.20 kbfix6.00 |
Last Reviewed: March 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |