3 ms·
From what I saw, started as routine maintenance, and we began seeing SQL timeouts and errors on SQL East, and then all our DB servers on SQL East just vanished.
by photorized 14y ago
From what I saw, started as routine maintenance, and we began seeing SQL timeouts and errors on SQL East, and then all our DB servers on SQL East just vanished. Stayed gone for 5 hours at least.
I took a screenshot of the status console once it got updated with the outage info (several hours into the outage):
https://mobile.twitter.com/iTrendTV/status/303959900164341760/photo/1 https://mobile.twitter.com/iTrendTV/status/30395990016434176...
Pretty unhappy about the whole experience. Luckily, we have our own colo in addition to Azure.
If you want to see people's reactions as this event unraveled:
http://social.msdn.microsoft.com/Forums/en-US/ssdsgetstarted/thread/231c1231-c634-448d-966f-40980c32460d http://social.msdn.microsoft.com/Forums/en-US/ssdsgetstarted...
- jspaur 14y agoOuch, we saw a similar thing in the South when things went sideways late last year. We've taken a similar approach to Sql Azure, use DataSync to replicate to offsite warm instances.