FIX: Log Shipping: Cannot Change Role From Secondary to Primary When Database Names Are Different

Article translations Article translations
Article ID: 300497 - View products that this article applies to.
This article was previously published under Q300497
BUG #: 235878 (SHILOH_BUGS)
Expand all | Collapse all


When using log shipping with a primary server and two secondary servers, the log shipping monitor may fail to update the remaining secondary node after a role change if the shipped database name is not the same on all servers.


The log shipping tool assumes that the database name is the same on both primary and secondary server(s). The shipping plan is for the database as named on the primary server.


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 INF: How to Obtain the Latest SQL Server 2000 Service Pack


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 1.


For additional information, see SQL Server 2000 Books Online and the following links:
"Log Shipping"

"How to set up and perform a log shipping role change"





Article ID: 300497 - Last Review: February 22, 2007 - Revision: 1.4
  • Microsoft SQL Server 2000 Enterprise Edition
kbbug kbfix kbsqlserv2000sp1fix kbsqlservlogship KB300497

Give Feedback


Contact us for more help

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