Article ID: 279793 - View products that this article applies to.
This article was previously published under Q279793
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57641 (SQLBUG_70)
If a table with an identity column is created and then subsequently dropped in the same transaction, and this transaction does not commit before the server shuts down abnormally, recovery of the database may fail with the following error message:
Be aware that you cannot associate all suspect databases with this issue. This problem is very timing-specific. The time between when the drop table command is executed and the server shuts down abnormally is important.
Error: 602, Severity: 21, State: 16.
Cannot recover the %databasename% database.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799For more information, contact your primary support provider.
(https://support.microsoft.com/kb/274799/ )INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
This problem is prevented with the application of SP3. However, SP3 does not resolve the issue if the customer has a database that is suspect. The customer still needs to restore from a backup or contact technical support for the usual assistance with a suspect database.