FIX: Transaction Log Space Grows on Standby Server

Article translations Article translations
Article ID: 279505 - View products that this article applies to.
This article was previously published under Q279505
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55450 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

The percentage of log space reported as in use may be incorrect on a standby server that is being used by log shipping or as a hot standby server when the logs are restored using the WITH STANDBY option. This behavior is observed only when an index creation operation spans a log backup on the primary server that is subsequently restored on the standby server. You will see a higher value reported for the percentage of log space in use on the standby server than on the primary server.

STATUS

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:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 279505 - Last Review: October 21, 2013 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB279505

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com