Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Configure Log Shipping Between SQL 2005 and SQL2008 Expand / Collapse
Author
Message
Posted Friday, January 16, 2009 1:10 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 3, 2010 2:49 PM
Points: 3, Visits: 20
I am trying to find out if it is possible to configure Logshipping between SQL Server 2008 and SQL Server 2005.

Has anyone tried it or can point me to any article?

Thank You
Post #638465
Posted Friday, January 16, 2009 2:16 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, March 18, 2014 12:13 PM
Points: 195, Visits: 1,080
I tried on my laptop where both SQL 2005 and SQL 2008 Standard Edition are installed. And found the following:

--If set the 2005 instnace as primary, it won't let me add the 2008 instance as secondary, as it is beyond its scope.

--If set the 2008 instnace as primary, i will not even be able to initialize the Logshipping, i.e. not be able to restore the fullbackup of the 2008 db onto the targeted (secondary) 2005 instance. Guess, again, the 2005 engine doesn't recognize the 2008 backup.

So I guess the answer would be NO..
Post #638517
Posted Friday, January 16, 2009 2:44 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:51 AM
Points: 6,266, Visits: 2,028
That information is actually not correct.

You CAN do LogShipping from 2005 to 2008 (without STANDBY mode)

You are requiered to use SQL 2008 UI tools ... if You want to use UI for configuration.



* Noel
Post #638536
Posted Friday, January 16, 2009 3:13 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, March 18, 2014 12:13 PM
Points: 195, Visits: 1,080
Sorry for the incorrect answer above.

Yes, noeld is correct. It can be done to logshipping SQL 2005 DB to a SQL 2008 Server.

Connect to the SQL2005 instance within your SQL2008 management studio.
Then configure the logshipping for the 2005 DB as primary from there...it will go through smoothly..

Thanks for the correction, noeld.
Post #638551
Posted Friday, January 16, 2009 3:18 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:51 AM
Points: 6,266, Visits: 2,028
sunny Brook (1/16/2009)
Sorry for the incorrect answer above.

Yes, noeld is correct. It can be done to logshipping SQL 2005 DB to a SQL 2008 Server.

Connect to the SQL2005 instance within your SQL2008 management studio.
Then configure the logshipping for the 2005 DB as primary from there...it will go through smoothly..

Thanks for the correction, noeld.


It was not my intention to put this bluntly.
I am sorry if it looked like that.

I was simply trying to help the PO.



* Noel
Post #638558
Posted Saturday, January 17, 2009 9:28 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, July 11, 2014 10:29 PM
Points: 2,007, Visits: 6,077
Just ensure to set the destination as NO RECOVERY and not STANDBY.



Shamless self promotion - read my blog http://sirsql.net
Post #638709
Posted Monday, August 27, 2012 3:54 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, July 25, 2014 3:08 AM
Points: 16, Visits: 201
Hi,

If we keep SQL 2005 as primary and 2008 as secondry :-

The databases don't get upgraded along the way. The upgrade doesn't occur until the database is recovered. For this reason, it is not possible to log ship up version in stand-by mode. You can do it if you leave the database offline (restoring mode). If you try to use stand-by mode, you'll get an error message stating that the backup is from a different version of SQL Server becuase it can't run crash recovery until the database is upgraded.

What is your motivation behind Log Shipping? Log shipping is often used to provide a warm standby. If you use it in this way and you need to fail over to the standby server, you now have no way to swap the log shipping roles, as you can't then log ship back from the 2008 server to the 2005 server.

Regards
Sachin
Post #1350291
Posted Monday, August 27, 2012 6:27 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, July 25, 2014 10:03 AM
Points: 1,312, Visits: 2,482
Sachin Butala-182900 (8/27/2012)
Hi,

If we keep SQL 2005 as primary and 2008 as secondry :-

The databases don't get upgraded along the way. The upgrade doesn't occur until the database is recovered. For this reason, it is not possible to log ship up version in stand-by mode. You can do it if you leave the database offline (restoring mode). If you try to use stand-by mode, you'll get an error message stating that the backup is from a different version of SQL Server becuase it can't run crash recovery until the database is upgraded.

What is your motivation behind Log Shipping? Log shipping is often used to provide a warm standby. If you use it in this way and you need to fail over to the standby server, you now have no way to swap the log shipping roles, as you can't then log ship back from the 2008 server to the 2005 server.

Regards
Sachin


+1

While it is possible to configure the log shipping from SQL Server 2005 to SQL Server 2008, keep it in mind that once you performed the failover you will not be able to restore your databases back on SQL Server 2005 again.



Sujeet Singh
Post #1350346
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse