This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469415 (SQL Server 8.0)
If transaction log stalls occur, a computer running SQL Server may experience CPU usage that was not expected. This usage occurs because of poor log file performance or because database backups are in progress.
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 fix 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 at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
The problem can be triggered by snapshot backups because the snapshot backup process involves the freeze and thaw of I/O operations. The freeze activity holds up all physical I/O activity until the thaw is issued at the end of the snapshot backup operation. In doing so, a code change that was made in SQL Server 2000 Service Pack 2 (SP2) results in heavier CPU usage than in earlier versions of SQL Server. The scalability change in SQL Server 2000 SP2 makes the log code scale better on multiprocessor computers. This change can, however, result in heavier CPU usage under rare conditions.