INF: CHECKALLOC/NEWALLOC & CHECKPOINT/DUMP TRANS SerializedLast reviewed: April 29, 1997Article ID: Q115068 |
The information in this article applies to:
- Microsoft SQL Server version 4.2 for OS/2 - Microsoft SQL Server version 4.2
SUMMARYIf a CHECKPOINT or DUMP TRANSACTION (which performs a CHECKPOINT) is executed while CHECKALLOC or NEWALLOC is running in the same database, it will wait on the CHECKALLOC/NEWALLOC to finish before proceeding. This is expected behavior and is caused by the need to serialize CHECKPOINT and certain internal server operations performed by CHECKALLOC/NEWALLOC.
MORE INFORMATIONSince DUMP TRANSACTION/CHECKPOINT is waiting on an internal flag and not on a lock, the stored procedures sp_who and sp_lock will not provide any indication of this behavior. Therefore, if DUMP TRANSACTION or a CHECKPOINT appears to be taking longer than usual, make sure there is no concurrent CHECKALLOC or NEWALLOC in progress. This behavior should have little operational impact. This is because to eliminate spurious errors it is always advisable to run CHECKALLOC or NEWALLOC while there is no activity in the database.
|
Additional query words: Windows NT
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |