Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Production Move


Production Move

Author
Message
AAKR
AAKR
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 439
Hi All,
I am going to a move a server to production. The present production is 2005 enterprise, now i am going to move this production to 2008 r2 slandered.
Here is my Question
What are the steps to follow to move server to production?
If something happen to the production what are the steps to rollback?
Could you please give me some suggestions?

In advance
Thank you 

Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8213 Visits: 14368
AAKR (5/1/2013)
Hi All,
I am going to a move a server to production. The present production is 2005 enterprise, now i am going to move this production to 2008 r2 slandered.
Here is my Question
What are the steps to follow to move server to production?
If something happen to the production what are the steps to rollback?
Could you please give me some suggestions?

In advance
Thank you 

Start by running the Upgrade Advisor against your current databases and resolve any recommendations it makes regarding compatibility. Since you are moving from Enterprise Edition to Standard Edition you'll also want to make sure you are not using any Enterprise-only features that may cease to function when you migrate.

My preference is to install a new instance so that in the event the migration goes poorly and we do not proceed on the new instance, we simply bring operations back online on the pre-existing instance.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44804 Visits: 39846
opc.three (5/1/2013)
AAKR (5/1/2013)
Hi All,
I am going to a move a server to production. The present production is 2005 enterprise, now i am going to move this production to 2008 r2 slandered.
Here is my Question
What are the steps to follow to move server to production?
If something happen to the production what are the steps to rollback?
Could you please give me some suggestions?

In advance
Thank you 

Start by running the Upgrade Advisor against your current databases and resolve any recommendations it makes regarding compatibility. Since you are moving from Enterprise Edition to Standard Edition you'll also want to make sure you are not using any Enterprise-only features that may cease to function when you migrate.

My preference is to install a new instance so that in the event the migration goes poorly and we do not proceed on the new instance, we simply bring operations back online on the pre-existing instance.

+1 to all of that.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
     Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
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