Creating Log Shipping between SQL SERVER 2008 & SQL SERVER 2000

  • Is it possible to create a log shipping between SQL SERVER 2008(Main Server,which transaaction logs are being copied) and SQL SERVER 2000(Subscriber,Which recieve the Transaction logs)?

    Thanks in advance

  • I'm not sure, but it's probably possible.

    However, I can see all kinds of problems coming up from it, even if it is possible. What happens if one of the columns being shipped is a data type that SQL 2000 doesn't support? And so on.

    It seems like a bad idea to me, because of that kind of issue.

    Is there a reason you have to do that?

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Actually,The Database that we are using in Log shipping ,it includes only SQL SERVER 2000 data types, and we do not have any problem with that.Just is it possible to configure log shipping between SQL SERVER 2008 and SQL SERVER 2000

  • No.

    The other way you can roll your own, but not able to bring the databse up to standby - just no recovery or recovery.

    2008 --> 2000 no chance.

  • Thanks for your reply.

    you mean ,I can not use it in any combination.For instance,If I put Publisher and distributor in SLQ SERVER 2008 and Subscriber in SQL SERVER 2000,Does this work.Also,would you please explain more about the status of Database that you had mentioned.

    Thanks alot

  • you can write logshipping to work taking a 2000 database to a 2008 server.

    What it limits you to is that the database must either be in norecovery or full recovery on the logshipping destination.

    We use logshipping to provide a 'read only' periodically updated copy of the database to query for eg MIS or Adhoc queries we wouldn't dare to run against the main 'live' servers.

    To do this we bring the logs up restored 'with standby' - which leave it read only and you can apply further logs later.

    You can't do this between 2000 and 2008, as to get it to standby it has to update the internal structure - a non read only operation. But you can apply the logs, so that when you want to recover the database in an emergency you can do so at short notice. You just cant read it until then.

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

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