April 26, 2014 at 5:58 pm
I've got SQL Server 2008 R2 Developer Edition on my desktop (I think it's a 4 year old machine). I've decided to purchase the 2014 Developer Edition want to upgrade what I've got on my dev box, to that. Or would it be better to put it on a laptop? Anyway, in such a migration, what's the steps I should take? I'll tell you what I've done in the past.
1) I've made a note of where the .mdf and .ldf files are, and detach the databases from SQL.
2) I've uninstalled the older version of SQL Server.
3) I'd then install the newer version of SQL Server.
4) I'd attach the new version of SQL to the .mdf and .ldf files.
I'm now under the impression that doing it that way leaves the databases in the older schemas. Am I correct? Would it therefore be better if I performed a full backup of the databases and then uninstall SQL 2008 R2, install SQL 2014, perform database recoveries, specifying a location for the .mdf and .ldf files, etc.? Or am I messing things up more?
Rod
April 28, 2014 at 2:13 am
After the testing you can change the compitability level of the database to 2014. Also you can use sp_help_revlogin to migrate users. There are two aproach to the upgrade one is side-by-side and other is in-place upgrade.
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 28, 2014 at 4:22 am
Since it's a dev box, I'd just do an in-place upgrade. I recently did one for my 2012 system to move it to 2014. It just worked. You do have to remember to change the compatibility level on your databases, but that's about it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 28, 2014 at 9:53 pm
Thank you free_mascot and Grant.
Rod
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply