Today, I worked on a service request when our customer reported a performance issue for their Azure SQL Database. However, the CPU is low, and DATAIO and TLOG are not more than 20% of usage. So, in this case, what is the performance issue?
My lesson learned here is that reviewing these three counters are not enough to identify a performance issue, in this case, we found two important things that reveal the performance issue:
1) The first issue was the waiting stats (select * from sys.dm_os_wait_stats:(
2) The second point we found multiple timeouts that the client application dropped the connection after several time.
In this situation, as I mentioned in a previous article, enabling the Diagnostics Setting for your database is a good starting point when you are facing these types of issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.