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


upgrade fail/slow rollback?


upgrade fail/slow rollback?

Author
Message
sasken
sasken
Hall of Fame
Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)

Group: General Forum Members
Points: 3444 Visits: 1948
Hello,

I am planning to upgrade from SQL 2008 R2 SE to SQL 2012 SE in our prod env. The upgrade will be an inplace upgrade to a cluster environment from standalone. I ran the upgrade advisor and I got no unresolved issues. I already did this on our staging and test environments and upgrade was successful. But the thing is I havent noticed any performance improvement. However after upgrading it from 2008 R2 SE to 2012 SE in our production environment and after a day/two of monitoring if we notice a decrease in performance and then if we decide to rollback I will have to rely on restoring the full backups that I took before the upgrade process. But a day/two's worth of data is in the 2012 database and I will have to do a data compare and move over the new records to the 2008 R2 database. And the databases are almost a terabyte and this is going to be a slowprocess.

Can experts please share their inputs for a better rollback plan inplace of upgrade failure or upgrade rollback.

Thanks

“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
GilaMonster
GilaMonster
SSC Guru
SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)

Group: General Forum Members
Points: 217521 Visits: 46278
Sapen (8/25/2014)
But a day/two's worth of data is in the 2012 database and I will have to do a data compare and move over the new records to the 2008 R2 database. And the databases are almost a terabyte and this is going to be a slowprocess.


Yes, that's pretty much what you have to do. Rolling back something like that is not a decision to be taken lightly, it's going to involve a lot of work.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Ricardo Leka
Ricardo Leka
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 289
One other thing, after the upgrade to 2012 SE you apply the SP2 ? and the CU 1 ?
On the CU after the SP1 of the 2012 they resolve a lot of issues with performance.
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)

Group: General Forum Members
Points: 95863 Visits: 33013
There is no downgrade path. It's just a question of migrating your data structures and data down to the older version. Personally, I wouldn't do it.

If you're seeing performance issues, there's a good chance that's primarily in what would be considered edge cases. Instead of downgrading, I'd suggest tuning the queries and structures so that they perform better. There's not a massive known improvement in performance between most SQL Server versions. Rather it's incremental along with additions to behavior with the newer versions.

----------------------------------------------------
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)SSC Guru (217K reputation)

Group: General Forum Members
Points: 217521 Visits: 46278
Grant Fritchey (8/25/2014)
Instead of downgrading, I'd suggest tuning the queries and structures so that they perform better. There's not a massive known improvement in performance between most SQL Server versions. Rather it's incremental along with additions to behavior with the newer versions.


Seconded.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


WorkasDBA
WorkasDBA
Old Hand
Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)

Group: General Forum Members
Points: 332 Visits: 122
You are doing an upgrade on SQL Server Version as well Standalone/Cluster changes. I would assume there will be changes to the storage as well. It will be difficult to debug performance if too many changes are made ..can be the SQL version upgrade, change in storage, network with new cluster et al. I would suggest an upgrade on your standalone to SQL Server 2012 first. Then set up the cluster et al.
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