Hi -

I'm trying to do manual log shipping from a SQL 2k Installation to a SQL 2k5
installation. The destination db in SQL 2k5 is at SQL2k compatibility level.
I'm trying to restore "with standby" .. and recieve the following error
message:

Msg 3180, Level 16, State 1, Line 1
This backup cannot be restored using WITH STANDBY because a database upgrade
is needed. Reissue the RESTORE without WITH STANDBY.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

1) Does anyone know of a workaround for this that will keep a ~current,
queryable destination db ?

2) Does anyone know whether/when Microsoft will fix this SQL 2k5 bug ?

Thanks,

Steve

Steve M (Ste***@discussions.microsoft.com) writes:
Show quoteHide quoteThis is not likely to be a bug, but be entirely by design.

A previous restore from a previous version is not like a restore from
the same version, but there are a lot changes that need to be made. For
instance, in the case of SQL 2005 there is a completely new set of
system tables, and the old system tables are now views. There are also
changes to page format etc. It seems difficult to mix this with the
STANDBY option.

Not that the compatibility mode only controls certain behaviour to
permit old code to be running. The compatibility mode is also something
you can change whenever you like in whichever direction. It has thus
no relation to the physical format of the database.

BCP genric error
Problem on scripting stored procedures
Telling if SQL2005 is running
SMSS - script to new window uses sp_executesql?!
error importing data from Access to SQL Server