Planned maintenance scheduled April 23, 2019 at 23:30UTC (7:30pm US/Eastern) Planned maintenance scheduled April 23, 2019 at 23:30UTC (7:30pm 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)

A term for a woman complaining about things/begging in a cute/childish way

What initially awakened the Balrog?

Trademark violation for app?

How would a mousetrap for use in space work?

How to pronounce 伝統色

What is the meaning of 'breadth' in breadth first search?

How many morphisms from 1 to 1+1 can there be?

What is Adi Shankara referring to when he says "He has Vajra marks on his feet"?

Should a wizard buy fine inks every time he want to copy spells into his spellbook?

A letter with no particular backstory

Customizing QGIS plugins

Amount of permutations on an NxNxN Rubik's Cube

Is it fair for a professor to grade us on the possession of past papers?

What is the home of the drow in Flanaess?

Drawing spherical mirrors

How does light 'choose' between wave and particle behaviour?

Can a Beast Master ranger change beast companions?

Has negative voting ever been officially implemented in elections, or seriously proposed, or even studied?

preposition before coffee

What makes a man succeed?

What would you call this weird metallic apparatus that allows you to lift people?

How to write capital alpha?

How were pictures turned from film to a big picture in a picture frame before digital scanning?

What order were files/directories output in dir?



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



Planned maintenance scheduled April 23, 2019 at 23:30UTC (7:30pm 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)










121
















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 11:30 UTC (7:30PM 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 StackOverflow and one for StackExchange (Careers), each cluster contains 3 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 2012 to the servers already on Windows 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



















  • 35





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 10





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 8





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

    – Tim Stone
    Apr 12 at 19:17






  • 97





    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






  • 4





    @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






  • 30





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

    – Artemis Fowl
    Apr 12 at 21:35







  • 23





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

    – Michael Hampton
    Apr 13 at 1:29






  • 7





    @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







  • 45





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 5





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

    – TGrif
    Apr 13 at 18:33






  • 3





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

    – Housemd
    Apr 14 at 6:19






  • 3





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

    – LogicalBranch
    Apr 16 at 9:11







  • 2





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    Is the maintenance delayed?

    – smileycreations15
    2 days ago






  • 4





    It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?

    – Sean
    yesterday















121
















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 11:30 UTC (7:30PM 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 StackOverflow and one for StackExchange (Careers), each cluster contains 3 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 2012 to the servers already on Windows 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



















  • 35





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 10





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 8





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

    – Tim Stone
    Apr 12 at 19:17






  • 97





    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






  • 4





    @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






  • 30





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

    – Artemis Fowl
    Apr 12 at 21:35







  • 23





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

    – Michael Hampton
    Apr 13 at 1:29






  • 7





    @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







  • 45





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 5





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

    – TGrif
    Apr 13 at 18:33






  • 3





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

    – Housemd
    Apr 14 at 6:19






  • 3





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

    – LogicalBranch
    Apr 16 at 9:11







  • 2





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    Is the maintenance delayed?

    – smileycreations15
    2 days ago






  • 4





    It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?

    – Sean
    yesterday













121












121








121


9







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 11:30 UTC (7:30PM 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 StackOverflow and one for StackExchange (Careers), each cluster contains 3 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 2012 to the servers already on Windows 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 11:30 UTC (7:30PM 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 StackOverflow and one for StackExchange (Careers), each cluster contains 3 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 2012 to the servers already on Windows 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 24 mins ago







Taryn

















asked Apr 12 at 19:06









TarynTaryn

33k12125186




33k12125186







  • 35





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 10





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 8





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

    – Tim Stone
    Apr 12 at 19:17






  • 97





    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






  • 4





    @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






  • 30





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

    – Artemis Fowl
    Apr 12 at 21:35







  • 23





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

    – Michael Hampton
    Apr 13 at 1:29






  • 7





    @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







  • 45





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 5





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

    – TGrif
    Apr 13 at 18:33






  • 3





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

    – Housemd
    Apr 14 at 6:19






  • 3





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

    – LogicalBranch
    Apr 16 at 9:11







  • 2





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    Is the maintenance delayed?

    – smileycreations15
    2 days ago






  • 4





    It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?

    – Sean
    yesterday












  • 35





    I'll cross some fingers for you :P

    – Tim Stone
    Apr 12 at 19:12






  • 10





    @TimStone We need more than that. :)

    – Taryn
    Apr 12 at 19:15






  • 8





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

    – Tim Stone
    Apr 12 at 19:17






  • 97





    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






  • 4





    @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






  • 30





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

    – Artemis Fowl
    Apr 12 at 21:35







  • 23





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

    – Michael Hampton
    Apr 13 at 1:29






  • 7





    @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







  • 45





    🔺 Thanks for plenty of notice.

    – Rob
    Apr 13 at 2:03






  • 5





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

    – TGrif
    Apr 13 at 18:33






  • 3





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

    – Housemd
    Apr 14 at 6:19






  • 3





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

    – LogicalBranch
    Apr 16 at 9:11







  • 2





    Why are you using Windows Server?

    – Sean
    Apr 16 at 19:18






  • 2





    Is the maintenance delayed?

    – smileycreations15
    2 days ago






  • 4





    It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?

    – Sean
    yesterday







35




35





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




10




10





@TimStone We need more than that. :)

– Taryn
Apr 12 at 19:15





@TimStone We need more than that. :)

– Taryn
Apr 12 at 19:15




8




8





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




97




97





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




4




4





@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




30




30





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





23




23





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




7




7





@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





45




45





🔺 Thanks for plenty of notice.

– Rob
Apr 13 at 2:03





🔺 Thanks for plenty of notice.

– Rob
Apr 13 at 2:03




5




5





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




3




3





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




3




3





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





2




2





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





Is the maintenance delayed?

– smileycreations15
2 days ago





Is the maintenance delayed?

– smileycreations15
2 days ago




4




4





It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?

– Sean
yesterday





It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?

– Sean
yesterday










3 Answers
3






active

oldest

votes


















18














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








New contributor




connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



























    9














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






    share|improve this answer


















    • 4





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

      – Taryn
      yesterday


















    0














    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


















    • 1





      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
      39 mins ago


















    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    18














    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








    New contributor




    connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
























      18














      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








      New contributor




      connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















        18












        18








        18







        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








        New contributor




        connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        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








        New contributor




        connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered Apr 16 at 20:41









        connectyourchargerconnectyourcharger

        3215




        3215




        New contributor




        connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        connectyourcharger is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





















            9














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






            share|improve this answer


















            • 4





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

              – Taryn
              yesterday















            9














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






            share|improve this answer


















            • 4





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

              – Taryn
              yesterday













            9












            9








            9







            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 yesterday









            Meta Bug WizardMeta Bug Wizard

            10.4k42264




            10.4k42264







            • 4





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

              – Taryn
              yesterday












            • 4





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

              – Taryn
              yesterday







            4




            4





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

            – Taryn
            yesterday





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

            – Taryn
            yesterday











            0














            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


















            • 1





              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
              39 mins ago















            0














            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


















            • 1





              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
              39 mins ago













            0












            0








            0







            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 40 mins ago









            DuckisaduckisaduckDuckisaduckisaduck

            1225




            1225







            • 1





              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
              39 mins ago












            • 1





              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
              39 mins ago







            1




            1





            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
            39 mins ago





            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
            39 mins ago



            Popular posts from this blog

            Are there any AGPL-style licences that require source code modifications to be public? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Force derivative works to be publicAre there any GPL like licenses for Apple App Store?Do you violate the GPL if you provide source code that cannot be compiled?GPL - is it distribution to use libraries in an appliance loaned to customers?Distributing App for free which uses GPL'ed codeModifications of server software under GPL, with web/CLI interfaceDoes using an AGPLv3-licensed library prevent me from dual-licensing my own source code?Can I publish only select code under GPLv3 from a private project?Is there published precedent regarding the scope of covered work that uses AGPL software?If MIT licensed code links to GPL licensed code what should be the license of the resulting binary program?If I use a public API endpoint that has its source code licensed under AGPL in my app, do I need to disclose my source?

            2013 GY136 Descoberta | Órbita | Referências Menu de navegação«List Of Centaurs and Scattered-Disk Objects»«List of Known Trans-Neptunian Objects»

            Metrô de Los Teques Índice Linhas | Estações | Ver também | Referências Ligações externas | Menu de navegação«INSTITUCIÓN»«Mapa de rutas»originalMetrô de Los TequesC.A. Metro Los Teques |Alcaldía de Guaicaipuro – Sitio OficialGobernacion de Mirandaeeeeeee