5 ms·
I’ve been a long time Azure user, their SQL Azure product was very glitchy and had constant outages (“just add retries!”), it’s gotten better in the last year o
by plasma 6y ago
I’ve been a long time Azure user, their SQL Azure product was very glitchy and had constant outages (“just add retries!”), it’s gotten better in the last year or so, but it was totally unacceptable.
- jiggawatts 6y agoAFAIK that's a "feature", not a bug. They throttle concurrent requests and return a different error code compared to the on-premises SQL Server. I just watched a load test hit that issue, the developers cranked up the traffic until the response times were measured in minutes. At that point Azure SQL started throwing errors related to too many concurrent queries. Compared to just locking up or timing out, it's probably better. See: https://docs.microsoft.com/en-us/azure/azure-sql/database/resource-limits-logical-server#sessions-and-workers-requests https://docs.microsoft.com/en-us/azure/azure-sql/database/re... And: https://docs.microsoft.com/en-us/azure/azure-sql/database/resource-limits-vcore-elastic-pools#general-purpose-service-tier-generation-4-compute-platform-part-1 https://docs.microsoft.com/en-us/azure/azure-sql/database/re... E.g.: the 4-CPU pool has only 210 Max concurrent workers per pool, but if you think about it, that's over 50 queries running at once per CPU core, which is nuts!
- plasma 6y agoI’ve experienced that too, but these errors were literally “server is currently unavailable” and downtime. Ps: if you’re working on a production load system, and has decent traffic, lean towards premium/business critical tiers for true HA