Can, log shipping be set up with a SQL Server 2000 Publisher and SQL Server 2005 Subscriber?
Can log shipping be set up with a SQL Server 2000 Publisher and SQL Server 2005 Subscriber (via LiteSpeed or the native SQL Server)? Or with a SQL Server 2005 Publisher and SQL Server 2000 Subscriber?
Log Shipping between SQL 2000 and SQL 2005 is not possible, due to the limitations of Microsofts SQL Server.
For example: Using SQL Server 2000 as the source server and SQL Server 2005 as the destination server and the Database Maintenance Plan Wizard to configure Log Shipping. During this wizard, on the �Specify the Log Shipping Destinations� when clicking the ADD button to add the servers, under the Server Name drop down, only those servers that are already registered in your Enterprise Manager will display. Since you cannot register a SQL 2005 server under Enterprise Manager, it will never pop-up in the drop down menu, preventing the log shipping setup.
In SQL Server 2005 Management Studio, register a SQL 2000 server under Management Studio and right click on the SQL 2000 database. The option �Ship Transaction Logs� is not available under TASKS (as part of the SQL Server 2005 design)
In the example, SQL Server 2005 as the source server and SQL 2000 as the standby destination server, in SQL Server 2005 Management Studio, right click on a SQL 2005 database and go to TASKS Ship Transaction Logs. Enable the database for log shipping, add the Secondary server. If the secondary server is SQL 2000, the following error message will display:
�servername� is not a valid secondary server instance because it is not the correct version. Secondary server instances must be servers running SQL Server 2005 or later.
For additional information: http://blogs.msdn.com/sanchan/archive/2006/02/12/530651.aspx
Did this article solve an issue for you?
Leave a Comment
Thank you for your feedback for Topic Request
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.