Log Shipping from 2000 to 2005

> The conclusion I draw from all your comments is that log shipping is possible from 2000 to 2005 if
> the 2000 log shipping destination database is restored in NORECOVERY on the 2005 server. The log
> shipping in this scenario must be done with a custom solution and is not supported with either
> SSMS or Enterprise Manager.

Yes, it should be possible. I should add that what I've tested is to restore a few 2000 log backups
to 2005 using norecovery. This was all OK. I then did RESTORE DATABASE x WITH RECOVERY to verify
that this was possible. Also OK. You should run a test where you actually log ship (a series of
restore) so nothing strange happens over time (not that I can see what that would be).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/


"Cgal" wrote in message news:ujFHgNvkHHA.3472@TK2MSFTNGP04.phx.gbl...
> Everyone,
>
> Thanks for the reponses.
>
> The conclusion I draw from all your comments is that log shipping is possible from 2000 to 2005 if
> the 2000 log shipping destination database is restored in NORECOVERY on the 2005 server. The log
> shipping in this scenario must be done with a custom solution and is not supported with either
> SSMS or Enterprise Manager.
>
>
> "Tibor Karaszi" wrote in message
> news:uiMAg3skHHA.2552@TK2MSFTNGP06.phx.gbl...
>>> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
>>> since as soon as you do the restore to 2005, it wants to "update" the database.
>>
>> I've tried it ;-). You can restore the log as long as you specify NORECOVERY.
>>
>>
>>> Cgal, MIGHT work if you specify a standby file. let us know.
>>
>> This is where it doesn't work. Specifying STANDBY means SQL Server need to upgrade the database,
>> and then downgrading it when applying your next log backup, which isn't possible. So you get an
>> error if you specify STANDBY when restoring 2000 backup onto 2005.
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>>
>> "Greg D. Moore (Strider)" wrote in message
>> news:eCgyKiskHHA.4624@TK2MSFTNGP04.phx.gbl...
>>>
>>>
>>> "Tibor Karaszi" wrote in message
>>> news:ehcjHunkHHA.4676@TK2MSFTNGP02.phx.gbl...
>>>> I'd very much doubt that you can use the built-in support for log shipping. But you can roll
>>>> your own. Google and you will even find script written for you.
>>>>
>>>
>>> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
>>> since as soon as you do the restore to 2005, it wants to "update" the database.
>>>
>>> Cgal, MIGHT work if you specify a standby file. let us know.
>>>
>>>
>>>> --
>>>> Tibor Karaszi, SQL Server MVP
>>>> http://www.karaszi.com/sqlserver/default.asp
>>>> http://sqlblog.com/blogs/tibor_karaszi
>>>>
>>>>
>>>> "Cgal" wrote in message
>>>> news:%23j0xkdmkHHA.4848@TK2MSFTNGP05.phx.gbl...
>>>>> Can log shipping be configured from a SQL Server 2000 database to a SQL Server 2005 database?
>>>>> I have read some posts on the Microsoft forums that indicate that it may be possible if a
>>>>> backup of the SQL Server 2000 database is restored to SQL Server 2005 with NoRecovery. I have
>>>>> tried to set this up with Enterprise Manager but have not had any luck.
>>>>>
>>>>> I have searched the Microsoft documentation but have not found anything definitive.
>>>>>
>>>>> Please help.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Chris
>>>>>
>>>>
>>>
>>> --
>>> Greg Moore
>>> SQL Server DBA Consulting Remote and Onsite available!
>>> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>>>
>>>
>>
>>
>
>

> The conclusion I draw from all your comments is that log shipping is possible from 2000 to 2005 if
> the 2000 log shipping destination database is restored in NORECOVERY on the 2005 server. The log
> shipping in this scenario must be done with a custom solution and is not supported with either
> SSMS or Enterprise Manager.

Yes, it should be possible. I should add that what I've tested is to restore a few 2000 log backups
to 2005 using norecovery. This was all OK. I then did RESTORE DATABASE x WITH RECOVERY to verify
that this was possible. Also OK. You should run a test where you actually log ship (a series of
restore) so nothing strange happens over time (not that I can see what that would be).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/


"Cgal" wrote in message news:ujFHgNvkHHA.3472@TK2MSFTNGP04.phx.gbl...
> Everyone,
>
> Thanks for the reponses.
>
> The conclusion I draw from all your comments is that log shipping is possible from 2000 to 2005 if
> the 2000 log shipping destination database is restored in NORECOVERY on the 2005 server. The log
> shipping in this scenario must be done with a custom solution and is not supported with either
> SSMS or Enterprise Manager.
>
>
> "Tibor Karaszi" wrote in message
> news:uiMAg3skHHA.2552@TK2MSFTNGP06.phx.gbl...
>>> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
>>> since as soon as you do the restore to 2005, it wants to "update" the database.
>>
>> I've tried it ;-). You can restore the log as long as you specify NORECOVERY.
>>
>>
>>> Cgal, MIGHT work if you specify a standby file. let us know.
>>
>> This is where it doesn't work. Specifying STANDBY means SQL Server need to upgrade the database,
>> and then downgrading it when applying your next log backup, which isn't possible. So you get an
>> error if you specify STANDBY when restoring 2000 backup onto 2005.
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>>
>> "Greg D. Moore (Strider)" wrote in message
>> news:eCgyKiskHHA.4624@TK2MSFTNGP04.phx.gbl...
>>>
>>>
>>> "Tibor Karaszi" wrote in message
>>> news:ehcjHunkHHA.4676@TK2MSFTNGP02.phx.gbl...
>>>> I'd very much doubt that you can use the built-in support for log shipping. But you can roll
>>>> your own. Google and you will even find script written for you.
>>>>
>>>
>>> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
>>> since as soon as you do the restore to 2005, it wants to "update" the database.
>>>
>>> Cgal, MIGHT work if you specify a standby file. let us know.
>>>
>>>
>>>> --
>>>> Tibor Karaszi, SQL Server MVP
>>>> http://www.karaszi.com/sqlserver/default.asp
>>>> http://sqlblog.com/blogs/tibor_karaszi
>>>>
>>>>
>>>> "Cgal" wrote in message
>>>> news:%23j0xkdmkHHA.4848@TK2MSFTNGP05.phx.gbl...
>>>>> Can log shipping be configured from a SQL Server 2000 database to a SQL Server 2005 database?
>>>>> I have read some posts on the Microsoft forums that indicate that it may be possible if a
>>>>> backup of the SQL Server 2000 database is restored to SQL Server 2005 with NoRecovery. I have
>>>>> tried to set this up with Enterprise Manager but have not had any luck.
>>>>>
>>>>> I have searched the Microsoft documentation but have not found anything definitive.
>>>>>
>>>>> Please help.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Chris
>>>>>
>>>>
>>>
>>> --
>>> Greg Moore
>>> SQL Server DBA Consulting Remote and Onsite available!
>>> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>>>
>>>
>>
>>
>
>

"Tibor Karaszi" wrote in
message news:uiMAg3skHHA.2552@TK2MSFTNGP06.phx.gbl...
>> Tibor, I haven't tried, but I don't think you can do log-shipping here,
>> even rolling your own since as soon as you do the restore to 2005, it
>> wants to "update" the database.
>
> I've tried it ;-). You can restore the log as long as you specify
> NORECOVERY.

Nothing like reality to confirm something.

(Just went through an interview where they claimed I was wrong about how BCP
and BULK COPY recovery mode worked. Annoyed me so much I had to go home to
confirm I was right. I was...they were wrong. But they still think they're
right. Oh well.)


>
>
>> Cgal, MIGHT work if you specify a standby file. let us know.
>
> This is where it doesn't work. Specifying STANDBY means SQL Server need to
> upgrade the database, and then downgrading it when applying your next log
> backup, which isn't possible. So you get an error if you specify STANDBY
> when restoring 2000 backup onto 2005.

Ah ok, so the exact opposite of what I was thinking. But I can see taht.


>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/

Does this mean you're working over at SQL now or simply hawking a great
site?

(Great group of people there, I've met a few. When I'm 1/2 as good as any
of them I'll consider myself "pretty good". ;-)

"Tibor Karaszi" wrote in
message news:uiMAg3skHHA.2552@TK2MSFTNGP06.phx.gbl...
>> Tibor, I haven't tried, but I don't think you can do log-shipping here,
>> even rolling your own since as soon as you do the restore to 2005, it
>> wants to "update" the database.
>
> I've tried it ;-). You can restore the log as long as you specify
> NORECOVERY.

Nothing like reality to confirm something.

(Just went through an interview where they claimed I was wrong about how BCP
and BULK COPY recovery mode worked. Annoyed me so much I had to go home to
confirm I was right. I was...they were wrong. But they still think they're
right. Oh well.)


>
>
>> Cgal, MIGHT work if you specify a standby file. let us know.
>
> This is where it doesn't work. Specifying STANDBY means SQL Server need to
> upgrade the database, and then downgrading it when applying your next log
> backup, which isn't possible. So you get an error if you specify STANDBY
> when restoring 2000 backup onto 2005.

Ah ok, so the exact opposite of what I was thinking. But I can see taht.


>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/

Does this mean you're working over at SQL now or simply hawking a great
site?

(Great group of people there, I've met a few. When I'm 1/2 as good as any
of them I'll consider myself "pretty good". ;-)