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


inplace upgrade for 2014 to 2016 with readable secondary.


inplace upgrade for 2014 to 2016 with readable secondary.

Author
Message
tcronin 95651
tcronin 95651
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5733 Visits: 723
I will be taking a VMWARE based 2014 AG that has one active and one read only node and doing in place upgrade to 2016. Since the one node is read only is it better to upgrade that box first and then the primary?
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (391K reputation)SSC Guru (391K reputation)SSC Guru (391K reputation)SSC Guru (391K reputation)SSC Guru (391K reputation)SSC Guru (391K reputation)SSC Guru (391K reputation)SSC Guru (391K reputation)

Group: General Forum Members
Points: 391242 Visits: 42824
Not having done this, I would say yes. I base this on how I upgraded mirrored databases.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Subramaniam Chandrasekar
Subramaniam Chandrasekar
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3512 Visits: 531
tcronin 95651 - Wednesday, December 20, 2017 2:49 PM
I will be taking a VMWARE based 2014 AG that has one active and one read only node and doing in place upgrade to 2016. Since the one node is read only is it better to upgrade that box first and then the primary?

We'd an in place upgrade similar to this earlier nine months. But it was Physical server not VMware servers. In our case, We'd upgraded from SQL 2008 R2 to SQL 2014 actually. Firstly Created a new DB server with Win server 2012 R2 and restored our data warehouses and databases there. Cross checked the schema of all data repositories. Everything went fine afterwards.
My basic checks normally are,
Whether a new server was setup for in place upgrade ? If it is, then proceed for SQL 2016 installation and further steps.(backup and restore)
Regarding VMware in place upgrade to 2016, You'd need to follow these steps, ( Not sure but have a basic knowledge on VMware)
Maybe you could check the below link for more reference.
https://communities.vmware.com/thread/394183
Thanks
Subbu

Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)

Group: General Forum Members
Points: 212796 Visits: 18586
tcronin 95651 - Wednesday, December 20, 2017 2:49 PM
I will be taking a VMWARE based 2014 AG that has one active and one read only node and doing in place upgrade to 2016. Since the one node is read only is it better to upgrade that box first and then the primary?


yes, correct. The rolling upgrade scenario is applicable here.
However some prefer a clean install, it's entirely up to you.
I've never had too much issue with inplace upgrades of, Windows yes, but not sql

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Subramaniam Chandrasekar
Subramaniam Chandrasekar
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3512 Visits: 531
subramaniam.chandrasekar - Thursday, December 21, 2017 5:30 AM
tcronin 95651 - Wednesday, December 20, 2017 2:49 PM
I will be taking a VMWARE based 2014 AG that has one active and one read only node and doing in place upgrade to 2016. Since the one node is read only is it better to upgrade that box first and then the primary?

We'd an in place upgrade similar to this earlier nine months. But it was Physical server not VMware servers. In our case, We'd upgraded from SQL 2008 R2 to SQL 2014 actually. Firstly Created a new DB server with Win server 2012 R2 and restored our data warehouses and databases there. Cross checked the schema of all data repositories. Everything went fine afterwards.
My basic checks normally are,
Whether a new server was setup for in place upgrade ? If it is, then proceed for SQL 2016 installation and further steps.(backup and restore)
Regarding VMware in place upgrade to 2016, You'd need to follow these steps, ( Not sure but have a basic knowledge on VMware)
Maybe you could check the below link for more reference.
https://communities.vmware.com/thread/394183
Thanks
Subbu

Following my earlier post, I'd like to post some more here.

When you have vm ware based setup, first you need to decide whether go with sql upgrade only or hardware upgrade.

If it is related to hardware upgrade, initially you'll need to upgrade the actual physical server and its then reflected to Vm wares. Once you've upgraded the actual physical servers, then proceed for in place upgrade strategy for sql upgrade.

Please note that the hardware upgrade on actual physical servers based on your requirement.

Hope I clarified your part of doubts.

Thanks
Subbu

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