Post reply

Enquiry on Logshipping

  • May 16, 2016 at 2:21 am

    #310642

    Hi,

    Is it possible to implement logshipping using SQL 2005 as a Source and SQL 2012 as Destination? Has anyone tried it before.

    SQL 2005 (Windows 2003)

    SQL 2012 (Windows 2012)

    the reason I ask is because we are migrating our databases from SQL 2005 to SQL 2012. Our client wants to have minimal downtime.

    If it is possible, then on the cutover date, we would just break the logshipping and bring up the secondary DB in SQL 2012. Then we will proceed to set up Always ON availablity Group (3-node AAG).

    Thank you.

    Best Regards

    Ricky

  • May 16, 2016 at 2:37 am

    #1879172

    Hi

    I think I got the answer already. I found the links below that gave me an idea.

    http://www.sqlservercentral.com/Forums/Topic638465-146-1.aspx

    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/13e50a4f-05bd-4abd-a1d7-73d2abca4013/log-shipping-between-sql-2005-and-sql-2012-log-restore-problem?forum=sqldisasterrecovery

    Thanks.

    Best Regards,

  • May 16, 2016 at 3:17 am

    #1879180

    Yup, entirely possible. Rolling upgrades like you describe are the only time that log shipping (or mirroring) is supported across versions.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • May 17, 2016 at 12:18 pm

    #1879650

    Agreed w/all above. Tis possible. However, you may want to consider any issues you may encounter because of differences between the two editions. Something as simple as the EOMONTH function will work in one and not the other. Might want to set the compatibility on the 2012 database to 2005 (if possible).

  • May 17, 2016 at 12:28 pm

    #1879657

    While you can set the compat mode, it won't do anything about the EOMonth function. That's new on 2012 and will work no matter the compat mode. Compatibility mode affects behaviour that has changed, not new features.

    Besides, the log shipping's there for the purposes of the rolling upgrade only. Once the 2012 instance is active, there's no going back, the other instance will either have to be upgraded or removed. You can't log ship from 2012 to 2005.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply