April 17, 2012 at 7:59 pm
I'm having problems restoring the transaction logs to the secondary server db because the transaction logs were created on sql server 2005 and the error message says that the logs need to be upgraded. Any way to get around this or should I just use replication because I know that will work.
Thanks in advance
April 18, 2012 at 1:49 am
Log shipping works up-version, the only thing is that the DB and logs on the secondary have to be restored WITH NORECOVERY. STANDBY is not an option when the primary and secondary are different versions.
That said, I generally don't recommend log shipping to a different version unless it's as part of an upgrade scenario. It's not a very useful DR setup as if you ever do have to use the secondary, there will be no way to move the database back to the primary server after the primary server is fixed without upgrading SQL on there.
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
April 18, 2012 at 5:36 am
thank you that's what I was thinking.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply