Couldn't connect to West Europe SQL Databases last week? Blame operator error

Microsoft has blamed "operator error" for the multi-hour outage of its cloud SQL Server in Europe last week. "Between 03:47 UTC and 13:30 UTC on 21 July 2022, customers using SQL Database and SQL Data Warehouse in West Europe may have experienced issues accessing services," said Microsoft. The issues were severe for affected …

[Pascal Monett]

"stronger guardrails 'to prevent human errors' "

Sounds like better procedures should be used.

But that sounds like work . . .

[Doctor Syntax]

"the company is to take a long, hard look at service resiliency."

Surely it's been looking already. Oh, sorry, I read that as "for" not "at".

[Mike 137]

"It was not explained how one person could wreak such havoc"

Poor process control. Just like the famous leap year Azure collapse. When you operate on the basis of least effort for maximum return, such events are to be expected.

[Warm Braw]

Revive the caches or rebuild entirely new ones

The whole point of a cache is you should be able to just trash it -or any part of it - and carry on as normal, albeit with temporarily degraded performance. If it were a true cache, you'd just push the query upstream and save the response for later reuse.

It appears that by "cache" they actually mean "replica" and if they can't get the basic terminology right, it's hardly surprising some operator gets confused about what they're doing.

[Anonymous Coward]

Cloud services are so much more reliable

Not.