Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Migratioon or Upgradaion Expand / Collapse
Author
Message
Posted Monday, August 25, 2014 5:53 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, December 18, 2014 11:33 AM
Points: 673, Visits: 907
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,
Post #1607023
Posted Monday, August 25, 2014 5:56 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 1:33 PM
Points: 2,533, Visits: 7,116
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.
Post #1607026
Posted Monday, August 25, 2014 6:47 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:35 PM
Points: 4,618, Visits: 4,076
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.

+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
Post #1607045
Posted Monday, August 25, 2014 7:41 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:26 AM
Points: 14,205, Visits: 28,536
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
Post #1607072
Posted Monday, August 25, 2014 8:15 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: 2 days ago @ 3:11 PM
Points: 31,368, Visits: 15,837
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
Post #1607089
Posted Monday, August 25, 2014 8:16 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, December 18, 2014 11:33 AM
Points: 673, Visits: 907
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.
Post #1607090
Posted Monday, August 25, 2014 8:23 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:26 AM
Points: 14,205, Visits: 28,536
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
Post #1607094
Posted Monday, August 25, 2014 4:32 PM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, December 18, 2014 11:33 AM
Points: 673, Visits: 907
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.
Post #1607287
Posted Monday, August 25, 2014 9:10 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: 2 days ago @ 3:11 PM
Points: 31,368, Visits: 15,837
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
Post #1607317
Posted Monday, August 25, 2014 11:33 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, October 17, 2014 8:25 AM
Points: 23, Visits: 142
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.
Post #1607335
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse