SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Migratioon or Upgradaion


Migratioon or Upgradaion

Author
Message
ramana3327
ramana3327
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2151 Visits: 2083
Hi,

If we want to move SQL Sever 2008R2 to SQL 2102,

In placemigration (Upgradation) or side by side migration is better? How can we decide which one is better option to us?

[url=http://sqlmag.com/blog/reasons-avoid-sql-server-place-upgrades][/url]This article showing that it is always better to avoid in place migration

Thanks,
Eirikur Eiriksson
Eirikur Eiriksson
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15648 Visits: 18624
ramana3327 (8/25/2014)
Hi,

If we want to move SQL Sever 2008R2 to SQL 2102,

In placemigration (Upgradation) or side by side migration is better? How can we decide which one is better option to us?

[url=http://sqlmag.com/blog/reasons-avoid-sql-server-place-upgrades][/url]This article showing that it is always better to avoid in place migration

Thanks,


Quick thought, my preferred method is (when possible) to do a side by side installation of SQL2012 and then copy everything over, test it and drop the source.
Cool
Ed Wagner
Ed Wagner
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17071 Visits: 10094
Eirikur Eiriksson (8/25/2014)
ramana3327 (8/25/2014)
Hi,

If we want to move SQL Sever 2008R2 to SQL 2102,

In placemigration (Upgradation) or side by side migration is better? How can we decide which one is better option to us?

[url=http://sqlmag.com/blog/reasons-avoid-sql-server-place-upgrades][/url]This article showing that it is always better to avoid in place migration

Thanks,


Quick thought, my preferred method is (when possible) to do a side by side installation of SQL2012 and then copy everything over, test it and drop the source.
Cool

+1. Side by side is safer. It completely avoids the risk of in-place upgrade. Your rollback plan is to simply revert back to using the original.


Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41675 Visits: 32666
Side-by-side is absolutely the best and safest. I've never really seen any major issues during upgrades, but if you had any, the ability to instantly just bring the old server online is the prefect safety mechanism.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Steve Jones
Steve Jones
SSC Guru
SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)

Group: Administrators
Points: 65043 Visits: 19118
Side by side for me, but always make sure you take backups of all user databases, master, model, and msdb before you do either.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
ramana3327
ramana3327
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2151 Visits: 2083
Thanks for the replies.

One more doubt about the downtime

"Downtime is the time to take the backup and restore into the new server and changing the compatibility levels and fixing the orphan users issues"

which option is better for databases recovery in side by side migration. If both sql 2008 r2 & 2012 will be in the same network and we need less downtime

1)Back up the databases from the original server and then restore them to the SQL Server 2012 instance. 2)Manually detach your database from the old instance and reattach it to the new instance
3)Use log shipping, or database mirroring.
4)Using the Copy Database Wizard to migrate databases to the new server.
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41675 Visits: 32666
1 or 3. But you should do the backups even if you do #3. The backups should just be how you protect yourself.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
ramana3327
ramana3327
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2151 Visits: 2083
Hi All,

Thanks for the replies.

I read that for migration we can schedule log backup or differential backup to reduce the downtime. Anyone did this? I need the downtime as less as possible.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)SSC Guru (65K reputation)

Group: Administrators
Points: 65043 Visits: 19118
The way you do this is to schedule full, then diffs, and then log backups. You take a full and restore it to the new instance. Once that is done, you can take a diff, and restore that to the new instance. Then logs.

If you time this right, you can get the downtime as low as a log or two of backup/copy/restore.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Wison
Wison
SSC Rookie
SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)

Group: General Forum Members
Points: 29 Visits: 151
If you have another server for migration and the server has the same or better hardware, you can do the side by side migration. and then you can control the migration progress.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search