Log shipping from SQL 2000 to SQL 2005

Is it possible to implement log shipping from SQL Server 2000 to SQL
Server 2005 where 2000 is the source and 2005 is the target. Can the
DB maintenance wizard be used, or does it need to be configured
manually?
Is log shipping possible where the source was 32 bit SQL 2000 and the
target is 64 bit SQL Server 2005?Hi
SQL Server 2000 can be the source, SQL Server 2005 can be the target, but
not the other way around. As long as the DB remains in the loading state
this will work.
Once you issue the RESTORE <db> WITH RECOVERY command, the DB on the target
server gets upgraded.
32 or 64 bit does not play a role as the file formats are the same for all
the processor editions.
There is a bit of work to do after you bring the DB online due to some
tables no longer being used in SQL Server 2005.
The log shipping jobs on SQL Server 2000 need to be removed and replaced by
SQL Server 2005 log shipping. In effect, you need to re-configure log
shipping as soon as SQL Server 2005 gets involved.
There is a good set of instructions in BOL "Upgrading a SQL Server 2000 Log
Shipping Configuration"
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/70612059-b0d2-45a6-b74c-8cb3
b9bdc921.htm
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<luke.embree@.gmail.com> wrote in message
news:1131852208.603161.273030@.g14g2000cwa.googlegroups.com...
> Is it possible to implement log shipping from SQL Server 2000 to SQL
> Server 2005 where 2000 is the source and 2005 is the target. Can the
> DB maintenance wizard be used, or does it need to be configured
> manually?
> Is log shipping possible where the source was 32 bit SQL 2000 and the
> target is 64 bit SQL Server 2005?
>