asked
How do I reduce LOG_RATE_GOVERNOR waits in SQL Database
I have a client with a SQL Database in Azure and the highest wait type is LOG_RATE_GOVERNOR. Is the only option to upgrade to the next edition (P3) or to shard the database into multiple smaller once? With the P3 They will get 4times more DTU:s but the price is also 4times higher. The client is considering to move everything to "onpremises" SQL Server due to the performance issues and the cost of the P3 edition.
That's transactional in nature so the best way is probably to shard, not even to do the upgrade to the higher tier. So the costs wouldn't be four times or even two times as much, but it would be higher plus the work of setting up a sharding mechanism.
Thanks @grant! I thought so too, and created a small matrix to compare editions to find the optimal number of shards, price, DTU units and size. The best price/performance is 12 SQL Database S3. (Price is in SEK) Edition $/db DTU Size #db New DTU size Price P3 24971 800 500 1 800 500 24971 P2) 6243 200 500 1 200 500 6243 P1 3122 100 500 2 200 1000 6244 S3 504 100 250 12 1200 3000 6048 S2 504 50 250 12 600 3000 6048 S1 202 20 250 31 620 7750 6262 S0 101 10 250 62 620 15500 6262 B 34 5 2 184 920 368 6256
15 People are following this question.
