Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Planned...
What's the point of the test set?
C's equality operator on converted pointers
The Nth Gryphon Number
How long can equipment go unused before powering up runs the risk of damage?
Do I really need to have a message in a novel to appeal to readers?
How many time has Arya actually used Needle?
How does the math work when buying airline miles?
How to write capital alpha?
Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?
In musical terms, what properties are varied by the human voice to produce different words / syllables?
How much damage would a cupful of neutron star matter do to the Earth?
How many morphisms from 1 to 1+1 can there be?
Would it be easier to apply for a UK visa if there is a host family to sponsor for you in going there?
Project Euler #1 in C++
What to do with repeated rejections for phd position
Crossing US/Canada Border for less than 24 hours
Should a wizard buy fine inks every time he want to copy spells into his spellbook?
Flash light on something
Can a Beast Master ranger change beast companions?
Random body shuffle every night—can we still function?
How to run automated tests after each commit?
Why weren't discrete x86 CPUs ever used in game hardware?
Why are vacuum tubes still used in amateur radios?
Does the Mueller report show a conspiracy between Russia and the Trump Campaign?
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
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?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)
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: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
edited 23 mins ago
Meta Bug Wizard
10.4k42264
asked Apr 12 at 19:06
Taryn♦Taryn
33k12125186
|
show 10 more comments
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: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
edited 23 mins ago
Meta Bug Wizard
10.4k42264
asked Apr 12 at 19:06
Taryn♦Taryn
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
2 days ago
|
show 10 more comments
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: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
edited 23 mins ago
Meta Bug Wizard
10.4k42264
asked Apr 12 at 19:06
Taryn♦Taryn
33k12125186
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: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
discussion featured announcements
edited 23 mins ago
Meta Bug Wizard
10.4k42264
asked Apr 12 at 19:06
Taryn♦Taryn
33k12125186
edited 23 mins ago
Meta Bug Wizard
10.4k42264
asked Apr 12 at 19:06
Taryn♦Taryn
33k12125186
edited 23 mins ago
Meta Bug Wizard
10.4k42264
edited 23 mins ago
Meta Bug Wizard
10.4k42264
edited 23 mins ago
Meta Bug Wizard
10.4k42264
10.4k42264
asked Apr 12 at 19:06
Taryn♦Taryn
33k12125186
asked Apr 12 at 19:06
Taryn♦Taryn
33k12125186
asked Apr 12 at 19:06
Taryn♦Taryn
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
2 days ago
|
show 10 more comments
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
2 days ago
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
2 days ago
It's 8:03 PM Eastern and the site isn't read-only yet; is something wrong?
– Sean
2 days ago
|
show 10 more comments
3 Answers
3
active
oldest
votes
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
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.
add a comment |
How do we know if the maintenance has been finished already or not yet carried out?
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
4
We'll update this post once done or if delayed beyond April 18th.
– Taryn♦
yesterday
add a comment |
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?
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
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♦
2 hours ago
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
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.
add a comment |
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
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.
add a comment |
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
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.
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
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.
answered Apr 16 at 20:41
connectyourchargerconnectyourcharger
3215
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.
add a comment |
add a comment |
How do we know if the maintenance has been finished already or not yet carried out?
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
4
We'll update this post once done or if delayed beyond April 18th.
– Taryn♦
yesterday
add a comment |
How do we know if the maintenance has been finished already or not yet carried out?
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
4
We'll update this post once done or if delayed beyond April 18th.
– Taryn♦
yesterday
add a comment |
How do we know if the maintenance has been finished already or not yet carried out?
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
How do we know if the maintenance has been finished already or not yet carried out?
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
answered yesterday
Meta Bug WizardMeta Bug Wizard
10.4k42264
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
add a comment |
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
add a comment |
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?
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
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♦
2 hours ago
add a comment |
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?
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
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♦
2 hours ago
add a comment |
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?
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
1225
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?
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
1225
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
1225
answered 2 hours ago
DuckisaduckisaduckDuckisaduckisaduck
1225
answered 2 hours 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♦
2 hours ago
add a comment |
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♦
2 hours 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♦
2 hours 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♦
2 hours ago
add a comment |
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
2 days ago