This article has been archived. It is offered "as is" and will no longer be updated.
If you use the sp_indexoption system procedure to set the DisAllowPageLocks value on an index to true, no exclusive locks may be taken during a data manipulation language (DML) operation. This problem may occur when at least one incompatible lock is held on the table, and the currently running DML statement chooses a locking strategy that uses a table lock on the table.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
SQL Server automatically chooses page-level locking, row-level locking, or table-level locking. You do not have to set these options manually. However, expert users who know with certainty that a particular type of lock is appropriate can change the locking behavior. For additional information, see the "sp_indexoption" topic in SQL Server Books Online.