June 18, 2013 at 4:45 am
I was supposed to be migrating some 2008 (SP3) databases from old physical machines to new virtual machines. I was just going to do a straightforward backup, move file, restore, etc. etc.
At the last minute I've been told the new machines need to be running 2008R2, not 2008. As is usual where I work it's all seat of the pants stuff, and has to be done NOW. Help! What's the sequence of events here? (I've been Googling but I'm getting a lot of answers about how to restore an R2 database to 2008, but not the other way around.) I can't upgrade the current databases to R2, only the destination ones, which is what is complicating things.
I'm sorry if this is really simple; I've been ill for a week with a raging temperature and I can't think straight. Any help would be gratefully received.
June 18, 2013 at 4:52 am
Hang on, it will automatically upgrade the database for me if I restore it to a higher version, won't it? I just need to change the compatibility level?
June 18, 2013 at 5:19 am
Backup, copy, restore. Nothing different.
2008 and 2008 R2 have the same compatibility level - 100.
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
June 18, 2013 at 5:21 am
Thank you. I think the stress is getting to me; this stuff is basic. If I could delete this thread I would!
June 18, 2013 at 5:21 am
Restoring a database from an older version to a newer version (as in your case) shouldn't be a problem. As you've said, you just need to change the compatibility level.
As for restoring backwards (restoring a database from a newer version to an older one) is not supported. I think it is possible but not pretty.
Remember to take across your logins to the new server
June 18, 2013 at 5:26 am
SQLSACT (6/18/2013)
As for restoring backwards (restoring a database from a newer version to an older one) is not supported. I think it is possible but not pretty.
It's not that it's not supported, it's outright not possible, pretty or otherwise. You have to recreate the DB on the lower version.
Not that the OP asked about restoring to a lower version.
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
June 18, 2013 at 5:29 am
GilaMonster (6/18/2013)
SQLSACT (6/18/2013)
As for restoring backwards (restoring a database from a newer version to an older one) is not supported. I think it is possible but not pretty.It's not that it's not supported, it's outright not possible, pretty or otherwise. You have to recreate the DB on the lower version.
Not that the OP asked about restoring to a lower version.
I stand under correction here but I am almost 100% sure that I've come across an article that describes how to restore to a lower version.
June 19, 2013 at 6:24 am
GilaMonster (6/18/2013)
Backup, copy, restore. Nothing different.2008 and 2008 R2 have the same compatibility level - 100.
What you want to updatestats in this case too or is it not applicable? Much like moving from 2005 to 2008 or 2005 to 2012.
Steve
June 19, 2013 at 6:26 am
Steve-3_5_7_9 (6/19/2013)
GilaMonster (6/18/2013)
Backup, copy, restore. Nothing different.2008 and 2008 R2 have the same compatibility level - 100.
What you want to updatestats in this case too or is it not applicable?
Not so much. The relational engine is near-identical between 2008 and 2008 R2. Something like 5 minor changes and that's all.
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
June 19, 2013 at 6:29 am
Thanks for the info.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply