If a server that is running SQL Server experiences an abrupt shutdown, it may take a database a long time to recover at start up if all the following conditions are true:
The shutdown occurs shortly after an extremely large increase in transaction rate, and checkpoint has not run since the transaction rate increased dramatically.
When SQL Server unexpectedly shut down, there were several active transactions (more than several thousand).
SQL Server was not shut down "cleanly." Some examples of this type of shutdown include a SHUTDOWN WITH NOWAIT command, a sudden hardware failure, or a power outage that affected the server.
The sp_configure stored procedure setting recovery interval is set to a non-default value (the default value is 0).
The last item in the list (recovery interval set to a value greater than 0) is not required for the problem to occur; however, you will probably not experience this situation when recovery is interval is set to 0.
The conditions required for you to experience this problem are extremely narrow and only apply to a small subset of long recovery cases. In particular, if database recovery is taking a long time because the SQL Server service was cycled in the middle of a single, or a small number of large transactions (for example, index creation, index rebuilds, or large insert, update, or delete jobs), this issue is probably not contributing to the problem. In order for there to be a high chance that this problem will occur, there must be an extremely large number of transactions (typically more than 10,000) active at the moment that SQL Server is abruptly stopped.
Even in situations where all these conditions are met, it is not always a good idea to apply this fix when a long-running recovery is occurring. The reason it is not a good idea is that applying the fix and enabling the trace flag that you need requires you to stop and restart the SQL Server service. Stopping and restarting the service will abort the active recovery process. Much of the work that has already been completed in recovery will have to be repeated when you restart SQL Server. Therefore, the overall recovery time might increase.
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
After you apply the hotfix that is described in this article, start SQL Server by using trace flag 3428 as a startup parameter.
The English version of this hotfix has the file attributes (or later file attributes) 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.