Thank you Sponsors

Is it really HA when you upgrade from 2016 to 2017? Jeff Schmidt Is it really HA when you upgrade from 2016 to 2017?

Who is Jeff?

Who is this guy? Currently Sr. DBA at International Cruses and Excursions Started as an Accidental DBA in Y2K Used SQL 6.5 through 2017 Oracle Development – Learning MySQL Twitter @Jeffveg LinkedIn www.linkedin.com/in/jeffkschmidt Blog? If I have the time NoSchmidt.com Small Business Owner (why I don’t have much time to blog)

Who is this guy? Currently Sr. DBA at International Cruses and Excursions Started as an Accidental DBA in Y2K Used SQL 6.5 through 2017 Oracle Development – Learning MySQL Twitter @Jeffveg LinkedIn www.linkedin.com/in/jeffkschmidt Blog? If I have the time NoSchmidt.com Small Business Owner (why I don’t have much time to blog)

What is this all about?

What I’m attempting today. Create a HA cluster OS 2012R2 - SQL 2016 Join 2 OS 2016 boxes to the Windows cluster Join the SQL 2017 instances to the HA cluster Failover to the 2017 instance Remove SQL 2016 instances from HA Remove 2012R2 Boxes from the Windows cluster Shut off the old nodes Party like it’s 1999 (before I was a DBA) when it works

What has already been done. Domain Created, and DC turned on. All boxes have been joined to the domain SQL is running as an admin (I’m being lazy) SQL has been installed on all boxes The 2 2012R2 boxes already have a windows cluster running

Demo!

Things to know! This window cluster is not supported because of the skipped check Once the failover to the 2017 box happens there is no failing back over to 2016 The 2016 secondarys are not readable after the failover to 2017 Like any HA cluster the data/log directories need to be all the same Don’t forget to move users and SQL Agent jobs

Question?

Thank you Sponsors