Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30 pm US/Eastern) Planned...

What were wait-states, and why was it only an issue for PCs?

Why I cannot instantiate a class whose constructor is private in a friend class?

What's called a person who work as someone who puts products on shelves in stores?

The 'gros' functor from schemes into (strictly) locally ringed topoi

Was there ever a LEGO store in Miami International Airport?

What helicopter has the most rotor blades?

Can gravitational waves pass through a black hole?

What do you call an IPA symbol that lacks a name (e.g. ɲ)?

What does こした mean?

How was Lagrange appointed professor of mathematics so early?

Feather, the Redeemed and Dire Fleet Daredevil

What happened to Viserion in Season 7?

Is Bran literally the world's memory?

Simulate round-robin tournament draw

Is it appropriate to mention a relatable company blog post when you're asked about the company?

TV series episode where humans nuke aliens before decrypting their message that states they come in peace

What *exactly* is electrical current, voltage, and resistance?

Is there a possibility to generate a list dynamically in Latex?

Protagonist's race is hidden - should I reveal it?

Why does Java have support for time zone offsets with seconds precision?

Marquee sign letters

Why is water being consumed when my shutoff valve is closed?

Why did Israel vote against lifting the American embargo on Cuba?

How to begin with a paragraph in latex



Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30 pm US/Eastern)



Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30 pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?The Many Memes of MetaWhich tools and technologies are used to build the Stack Exchange Network?Recent Reputation History ChangesStack Overflow is getting a Meta of its ownOperation 'Split, All The Metas!' Shall Commence On April 16, 2014Brief outage planned for Wed, May 3, 2017 at 8pm US/Eastern (00:00 UTC) (like a fire drill for computers)Brief maintenances planned for Sat, July 8 & 22, 2017 both at 14:00 UTC (10AM US/Eastern)Brief maintenances planned for Sat, July 22, 2017 at 00:01 UTC (Fri July 21, 8pm US/Eastern)What criteria should we use to determine which review queue indicator a site will have?Planned maintenance scheduled for March 17, 2018 at 13:00 UTC (9AM US/Eastern)Brace yourselves: The GDPR is coming!Planned maintenance scheduled for July 14, 2018 at 13:00 UTC (9AM US/Eastern)












137
















Current status We have hit some unexpected issues and have rescheduled - title and dates below are updated. The work listed below for Monday/Tuesday has already been completed, the rest of the work will be completed on the day we perform the failover.






tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.



Short Version:



There will be a service degradation for up to an hour this upcoming week - possibly April 23rd, 2019 at 23:30 UTC (7:30 PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.



Longer More Technical Version of What’s Happening?



Background



Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for Stack Overflow and one for Stack Exchange (Careers), each cluster contains three database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows Server 2012 to the servers already on Windows Server 2016.



What we'll be doing



As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.



This upgrades involves many moving pieces, but high-level we will be doing the following next week:




  • Monday: we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.


  • Tuesday: another NY Secondary will follow the same path as the one on Monday.


  • Wednesday: the remote secondaries in CO will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters.



At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) . If anything gets delayed or if there are unexpected issues, then we will push the maintenance to later.



We will not be moving forward with the failover until we are comfortable.



When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.



This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:




Everyone has a plan until they get punched in the mouth - Mike Tyson




Questions or concerns?



Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.










share|improve this question




















  • 41





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 11





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 10





    Alright alright, I'll go buy some rum or something too

    – Tim Stone
    Apr 12 at 19:17






  • 107





    As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?

    – rene
    Apr 12 at 19:20






  • 5





    @rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.

    – Taryn
    Apr 12 at 19:24






  • 31





    Wait... will I have to... go to sleep!?

    – Artemis Fowl
    Apr 12 at 21:35








  • 26





    Looking forward to the upgrade to Server 2019 in six to eight weeks.

    – Michael Hampton
    Apr 13 at 1:29






  • 9





    @MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.

    – Taryn
    Apr 13 at 1:32








  • 51





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 7





    Banner text: We're 'read only' for 60 to 80 minutes for maintenance.

    – TGrif
    Apr 13 at 18:33






  • 4





    Why not take the AWS route, migrate to the cloud?

    – Housemd
    Apr 14 at 6:19






  • 6





    Ha! The AskDifferent, AskUbuntu and Unix StackExchange sites are running on Windows Server :)

    – LogicalBranch
    Apr 16 at 9:11








  • 4





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    @Makyen The plan was to make an update today, once we knew we were going forward. I have just added an update to the top of the post, since this is postponed until potentially next week.

    – Taryn
    Apr 18 at 19:04






  • 3





    @AndrewMorton Of course we'll share. We hit a significant bug within SQL Server and the Distributed AGs. Microsoft worked with us to get past the issue, but a fix will be released in the next CU.

    – Taryn
    2 days ago
















137
















Current status We have hit some unexpected issues and have rescheduled - title and dates below are updated. The work listed below for Monday/Tuesday has already been completed, the rest of the work will be completed on the day we perform the failover.






tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.



Short Version:



There will be a service degradation for up to an hour this upcoming week - possibly April 23rd, 2019 at 23:30 UTC (7:30 PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.



Longer More Technical Version of What’s Happening?



Background



Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for Stack Overflow and one for Stack Exchange (Careers), each cluster contains three database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows Server 2012 to the servers already on Windows Server 2016.



What we'll be doing



As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.



This upgrades involves many moving pieces, but high-level we will be doing the following next week:




  • Monday: we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.


  • Tuesday: another NY Secondary will follow the same path as the one on Monday.


  • Wednesday: the remote secondaries in CO will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters.



At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) . If anything gets delayed or if there are unexpected issues, then we will push the maintenance to later.



We will not be moving forward with the failover until we are comfortable.



When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.



This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:




Everyone has a plan until they get punched in the mouth - Mike Tyson




Questions or concerns?



Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.










share|improve this question




















  • 41





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 11





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 10





    Alright alright, I'll go buy some rum or something too

    – Tim Stone
    Apr 12 at 19:17






  • 107





    As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?

    – rene
    Apr 12 at 19:20






  • 5





    @rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.

    – Taryn
    Apr 12 at 19:24






  • 31





    Wait... will I have to... go to sleep!?

    – Artemis Fowl
    Apr 12 at 21:35








  • 26





    Looking forward to the upgrade to Server 2019 in six to eight weeks.

    – Michael Hampton
    Apr 13 at 1:29






  • 9





    @MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.

    – Taryn
    Apr 13 at 1:32








  • 51





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 7





    Banner text: We're 'read only' for 60 to 80 minutes for maintenance.

    – TGrif
    Apr 13 at 18:33






  • 4





    Why not take the AWS route, migrate to the cloud?

    – Housemd
    Apr 14 at 6:19






  • 6





    Ha! The AskDifferent, AskUbuntu and Unix StackExchange sites are running on Windows Server :)

    – LogicalBranch
    Apr 16 at 9:11








  • 4





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    @Makyen The plan was to make an update today, once we knew we were going forward. I have just added an update to the top of the post, since this is postponed until potentially next week.

    – Taryn
    Apr 18 at 19:04






  • 3





    @AndrewMorton Of course we'll share. We hit a significant bug within SQL Server and the Distributed AGs. Microsoft worked with us to get past the issue, but a fix will be released in the next CU.

    – Taryn
    2 days ago














137












137








137


11







Current status We have hit some unexpected issues and have rescheduled - title and dates below are updated. The work listed below for Monday/Tuesday has already been completed, the rest of the work will be completed on the day we perform the failover.






tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.



Short Version:



There will be a service degradation for up to an hour this upcoming week - possibly April 23rd, 2019 at 23:30 UTC (7:30 PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.



Longer More Technical Version of What’s Happening?



Background



Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for Stack Overflow and one for Stack Exchange (Careers), each cluster contains three database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows Server 2012 to the servers already on Windows Server 2016.



What we'll be doing



As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.



This upgrades involves many moving pieces, but high-level we will be doing the following next week:




  • Monday: we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.


  • Tuesday: another NY Secondary will follow the same path as the one on Monday.


  • Wednesday: the remote secondaries in CO will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters.



At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) . If anything gets delayed or if there are unexpected issues, then we will push the maintenance to later.



We will not be moving forward with the failover until we are comfortable.



When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.



This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:




Everyone has a plan until they get punched in the mouth - Mike Tyson




Questions or concerns?



Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.










share|improve this question

















Current status We have hit some unexpected issues and have rescheduled - title and dates below are updated. The work listed below for Monday/Tuesday has already been completed, the rest of the work will be completed on the day we perform the failover.






tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.



Short Version:



There will be a service degradation for up to an hour this upcoming week - possibly April 23rd, 2019 at 23:30 UTC (7:30 PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.



Longer More Technical Version of What’s Happening?



Background



Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for Stack Overflow and one for Stack Exchange (Careers), each cluster contains three database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows Server 2012 to the servers already on Windows Server 2016.



What we'll be doing



As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.



This upgrades involves many moving pieces, but high-level we will be doing the following next week:




  • Monday: we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.


  • Tuesday: another NY Secondary will follow the same path as the one on Monday.


  • Wednesday: the remote secondaries in CO will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters.



At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) . If anything gets delayed or if there are unexpected issues, then we will push the maintenance to later.



We will not be moving forward with the failover until we are comfortable.



When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.



This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:




Everyone has a plan until they get punched in the mouth - Mike Tyson




Questions or concerns?



Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.







discussion featured announcements






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago









Peter Mortensen

4,57442752




4,57442752










asked Apr 12 at 19:06









TarynTaryn

33.1k12125186




33.1k12125186








  • 41





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 11





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 10





    Alright alright, I'll go buy some rum or something too

    – Tim Stone
    Apr 12 at 19:17






  • 107





    As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?

    – rene
    Apr 12 at 19:20






  • 5





    @rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.

    – Taryn
    Apr 12 at 19:24






  • 31





    Wait... will I have to... go to sleep!?

    – Artemis Fowl
    Apr 12 at 21:35








  • 26





    Looking forward to the upgrade to Server 2019 in six to eight weeks.

    – Michael Hampton
    Apr 13 at 1:29






  • 9





    @MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.

    – Taryn
    Apr 13 at 1:32








  • 51





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 7





    Banner text: We're 'read only' for 60 to 80 minutes for maintenance.

    – TGrif
    Apr 13 at 18:33






  • 4





    Why not take the AWS route, migrate to the cloud?

    – Housemd
    Apr 14 at 6:19






  • 6





    Ha! The AskDifferent, AskUbuntu and Unix StackExchange sites are running on Windows Server :)

    – LogicalBranch
    Apr 16 at 9:11








  • 4





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    @Makyen The plan was to make an update today, once we knew we were going forward. I have just added an update to the top of the post, since this is postponed until potentially next week.

    – Taryn
    Apr 18 at 19:04






  • 3





    @AndrewMorton Of course we'll share. We hit a significant bug within SQL Server and the Distributed AGs. Microsoft worked with us to get past the issue, but a fix will be released in the next CU.

    – Taryn
    2 days ago














  • 41





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 11





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 10





    Alright alright, I'll go buy some rum or something too

    – Tim Stone
    Apr 12 at 19:17






  • 107





    As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?

    – rene
    Apr 12 at 19:20






  • 5





    @rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.

    – Taryn
    Apr 12 at 19:24






  • 31





    Wait... will I have to... go to sleep!?

    – Artemis Fowl
    Apr 12 at 21:35








  • 26





    Looking forward to the upgrade to Server 2019 in six to eight weeks.

    – Michael Hampton
    Apr 13 at 1:29






  • 9





    @MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.

    – Taryn
    Apr 13 at 1:32








  • 51





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 7





    Banner text: We're 'read only' for 60 to 80 minutes for maintenance.

    – TGrif
    Apr 13 at 18:33






  • 4





    Why not take the AWS route, migrate to the cloud?

    – Housemd
    Apr 14 at 6:19






  • 6





    Ha! The AskDifferent, AskUbuntu and Unix StackExchange sites are running on Windows Server :)

    – LogicalBranch
    Apr 16 at 9:11








  • 4





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    @Makyen The plan was to make an update today, once we knew we were going forward. I have just added an update to the top of the post, since this is postponed until potentially next week.

    – Taryn
    Apr 18 at 19:04






  • 3





    @AndrewMorton Of course we'll share. We hit a significant bug within SQL Server and the Distributed AGs. Microsoft worked with us to get past the issue, but a fix will be released in the next CU.

    – Taryn
    2 days ago








41




41





I'll cross some fingers for you :P

– Tim Stone
Apr 12 at 19:12





I'll cross some fingers for you :P

– Tim Stone
Apr 12 at 19:12




11




11





@TimStone We need more than that. :)

– Taryn
Apr 12 at 19:15





@TimStone We need more than that. :)

– Taryn
Apr 12 at 19:15




10




10





Alright alright, I'll go buy some rum or something too

– Tim Stone
Apr 12 at 19:17





Alright alright, I'll go buy some rum or something too

– Tim Stone
Apr 12 at 19:17




107




107





As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?

– rene
Apr 12 at 19:20





As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?

– rene
Apr 12 at 19:20




5




5





@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.

– Taryn
Apr 12 at 19:24





@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.

– Taryn
Apr 12 at 19:24




31




31





Wait... will I have to... go to sleep!?

– Artemis Fowl
Apr 12 at 21:35







Wait... will I have to... go to sleep!?

– Artemis Fowl
Apr 12 at 21:35






26




26





Looking forward to the upgrade to Server 2019 in six to eight weeks.

– Michael Hampton
Apr 13 at 1:29





Looking forward to the upgrade to Server 2019 in six to eight weeks.

– Michael Hampton
Apr 13 at 1:29




9




9





@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.

– Taryn
Apr 13 at 1:32







@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.

– Taryn
Apr 13 at 1:32






51




51





🔺 Thanks for plenty of notice.

– Rob
Apr 13 at 2:03





🔺 Thanks for plenty of notice.

– Rob
Apr 13 at 2:03




7




7





Banner text: We're 'read only' for 60 to 80 minutes for maintenance.

– TGrif
Apr 13 at 18:33





Banner text: We're 'read only' for 60 to 80 minutes for maintenance.

– TGrif
Apr 13 at 18:33




4




4





Why not take the AWS route, migrate to the cloud?

– Housemd
Apr 14 at 6:19





Why not take the AWS route, migrate to the cloud?

– Housemd
Apr 14 at 6:19




6




6





Ha! The AskDifferent, AskUbuntu and Unix StackExchange sites are running on Windows Server :)

– LogicalBranch
Apr 16 at 9:11







Ha! The AskDifferent, AskUbuntu and Unix StackExchange sites are running on Windows Server :)

– LogicalBranch
Apr 16 at 9:11






4




4





Why are you using Windows Server?

– Sean
Apr 16 at 19:18





Why are you using Windows Server?

– Sean
Apr 16 at 19:18




2




2





@Makyen The plan was to make an update today, once we knew we were going forward. I have just added an update to the top of the post, since this is postponed until potentially next week.

– Taryn
Apr 18 at 19:04





@Makyen The plan was to make an update today, once we knew we were going forward. I have just added an update to the top of the post, since this is postponed until potentially next week.

– Taryn
Apr 18 at 19:04




3




3





@AndrewMorton Of course we'll share. We hit a significant bug within SQL Server and the Distributed AGs. Microsoft worked with us to get past the issue, but a fix will be released in the next CU.

– Taryn
2 days ago





@AndrewMorton Of course we'll share. We hit a significant bug within SQL Server and the Distributed AGs. Microsoft worked with us to get past the issue, but a fix will be released in the next CU.

– Taryn
2 days ago










4 Answers
4






active

oldest

votes


















25














Just don't take too long. I don't know how long I'll be able to wait without commenting on, answering, or editing a post.



It is my life at this point.






share|improve this answer































    13














    How do we know if the maintenance has been finished already or not yet carried out?






    share|improve this answer



















    • 5





      We'll update this post once done or if delayed beyond April 18th.

      – Taryn
      Apr 18 at 12:34











    • It will be tweeted!

      – Chirag Jain
      2 days ago



















    11














    Once maintenance is complete, will we be treated to a blow by blow story, with personal drama, difficulties overcome, and maybe even a touch of tragedy and romance?






    share|improve this answer



















    • 11





      Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

      – Taryn
      Apr 19 at 21:52



















    2














    Taryn, Stack Overflow has a tiny unobtrusive banner reminding us. I don't see this on any of our other sites. Could this be added to all the sites and during the event a different banner (End: ETA) appear?



    Reminder Banner






    share|improve this answer



















    • 5





      This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

      – Taryn
      22 hours ago













    • @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

      – Meta Bug Wizard
      10 hours ago






    • 1





      @MetaBugWizard Nope, it's currently Daylight Saving Time.

      – Taryn
      10 hours ago



















    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    25














    Just don't take too long. I don't know how long I'll be able to wait without commenting on, answering, or editing a post.



    It is my life at this point.






    share|improve this answer




























      25














      Just don't take too long. I don't know how long I'll be able to wait without commenting on, answering, or editing a post.



      It is my life at this point.






      share|improve this answer


























        25












        25








        25







        Just don't take too long. I don't know how long I'll be able to wait without commenting on, answering, or editing a post.



        It is my life at this point.






        share|improve this answer













        Just don't take too long. I don't know how long I'll be able to wait without commenting on, answering, or editing a post.



        It is my life at this point.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 16 at 20:41









        connectyourchargerconnectyourcharger

        39115




        39115























            13














            How do we know if the maintenance has been finished already or not yet carried out?






            share|improve this answer



















            • 5





              We'll update this post once done or if delayed beyond April 18th.

              – Taryn
              Apr 18 at 12:34











            • It will be tweeted!

              – Chirag Jain
              2 days ago
















            13














            How do we know if the maintenance has been finished already or not yet carried out?






            share|improve this answer



















            • 5





              We'll update this post once done or if delayed beyond April 18th.

              – Taryn
              Apr 18 at 12:34











            • It will be tweeted!

              – Chirag Jain
              2 days ago














            13












            13








            13







            How do we know if the maintenance has been finished already or not yet carried out?






            share|improve this answer













            How do we know if the maintenance has been finished already or not yet carried out?







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 18 at 12:33









            Meta Bug WizardMeta Bug Wizard

            10.5k42266




            10.5k42266








            • 5





              We'll update this post once done or if delayed beyond April 18th.

              – Taryn
              Apr 18 at 12:34











            • It will be tweeted!

              – Chirag Jain
              2 days ago














            • 5





              We'll update this post once done or if delayed beyond April 18th.

              – Taryn
              Apr 18 at 12:34











            • It will be tweeted!

              – Chirag Jain
              2 days ago








            5




            5





            We'll update this post once done or if delayed beyond April 18th.

            – Taryn
            Apr 18 at 12:34





            We'll update this post once done or if delayed beyond April 18th.

            – Taryn
            Apr 18 at 12:34













            It will be tweeted!

            – Chirag Jain
            2 days ago





            It will be tweeted!

            – Chirag Jain
            2 days ago











            11














            Once maintenance is complete, will we be treated to a blow by blow story, with personal drama, difficulties overcome, and maybe even a touch of tragedy and romance?






            share|improve this answer



















            • 11





              Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

              – Taryn
              Apr 19 at 21:52
















            11














            Once maintenance is complete, will we be treated to a blow by blow story, with personal drama, difficulties overcome, and maybe even a touch of tragedy and romance?






            share|improve this answer



















            • 11





              Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

              – Taryn
              Apr 19 at 21:52














            11












            11








            11







            Once maintenance is complete, will we be treated to a blow by blow story, with personal drama, difficulties overcome, and maybe even a touch of tragedy and romance?






            share|improve this answer













            Once maintenance is complete, will we be treated to a blow by blow story, with personal drama, difficulties overcome, and maybe even a touch of tragedy and romance?







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 19 at 21:51









            DuckisaduckisaduckDuckisaduckisaduck

            23217




            23217








            • 11





              Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

              – Taryn
              Apr 19 at 21:52














            • 11





              Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

              – Taryn
              Apr 19 at 21:52








            11




            11





            Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

            – Taryn
            Apr 19 at 21:52





            Yes I will blog about it. If you have been following me or Nick on twitter, you'll notice things are not going well.

            – Taryn
            Apr 19 at 21:52











            2














            Taryn, Stack Overflow has a tiny unobtrusive banner reminding us. I don't see this on any of our other sites. Could this be added to all the sites and during the event a different banner (End: ETA) appear?



            Reminder Banner






            share|improve this answer



















            • 5





              This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

              – Taryn
              22 hours ago













            • @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

              – Meta Bug Wizard
              10 hours ago






            • 1





              @MetaBugWizard Nope, it's currently Daylight Saving Time.

              – Taryn
              10 hours ago
















            2














            Taryn, Stack Overflow has a tiny unobtrusive banner reminding us. I don't see this on any of our other sites. Could this be added to all the sites and during the event a different banner (End: ETA) appear?



            Reminder Banner






            share|improve this answer



















            • 5





              This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

              – Taryn
              22 hours ago













            • @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

              – Meta Bug Wizard
              10 hours ago






            • 1





              @MetaBugWizard Nope, it's currently Daylight Saving Time.

              – Taryn
              10 hours ago














            2












            2








            2







            Taryn, Stack Overflow has a tiny unobtrusive banner reminding us. I don't see this on any of our other sites. Could this be added to all the sites and during the event a different banner (End: ETA) appear?



            Reminder Banner






            share|improve this answer













            Taryn, Stack Overflow has a tiny unobtrusive banner reminding us. I don't see this on any of our other sites. Could this be added to all the sites and during the event a different banner (End: ETA) appear?



            Reminder Banner







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 22 hours ago









            RobRob

            3,45431239




            3,45431239








            • 5





              This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

              – Taryn
              22 hours ago













            • @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

              – Meta Bug Wizard
              10 hours ago






            • 1





              @MetaBugWizard Nope, it's currently Daylight Saving Time.

              – Taryn
              10 hours ago














            • 5





              This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

              – Taryn
              22 hours ago













            • @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

              – Meta Bug Wizard
              10 hours ago






            • 1





              @MetaBugWizard Nope, it's currently Daylight Saving Time.

              – Taryn
              10 hours ago








            5




            5





            This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

            – Taryn
            22 hours ago







            This was added specifically on Stack Overflow because of Teams and is only shown to users of Teams, so currently it’s limited to that and I don’t think there are plans to expand that banner elsewhere at this time. During the maintenance we will have the normal banner that states we are read-only for maintenance.

            – Taryn
            22 hours ago















            @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

            – Meta Bug Wizard
            10 hours ago





            @Taryn The banner reads 7:30 pm ET, shouldn't that be 7:30 pm EST?

            – Meta Bug Wizard
            10 hours ago




            1




            1





            @MetaBugWizard Nope, it's currently Daylight Saving Time.

            – Taryn
            10 hours ago





            @MetaBugWizard Nope, it's currently Daylight Saving Time.

            – Taryn
            10 hours ago



            Popular posts from this blog

            “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

            How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

            變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...