September 22, 2014 at 7:54 am
Hi Folks,
I like to understand, how you are handling the rollback process in SQL Upgrade. My usual approach (side by side) is that I upgrade the SQL Server and end to end testing should be conducted before going live. If any problem identified in testing we rollback or we roll-forward and complete the upgrade. But in case, if any problem occurs after going live there is no way to rollback, as there is no way we can gather the incremental data from the target server and put it back to source(until we get the script from the developer to do so which is out of consideration here). Am I right or Is there a way to get the incremental data?
Regards,
Satheesh.
---------------------------------------------------
Thanks,
Satheesh.
September 22, 2014 at 8:10 am
If you decide to run live on an upgraded server for any amount of time, you have the problem of rollback - whether you upgraded in place or did a side by side.
Sometimes, you can setup replication between the servers in a side by side scenario to help with that potential rollback.
Sometimes, you can use a tool such as RedGate SQL Data Compare to get the data back to the old prod box.
My question would be, "why proceed with putting the upgraded server into production mode if the testing has not been adequately completed?".
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply