If you have an application experiencing slow performance, one way to approach scoping this would be to use the Diagnose and solve problems blade in Portal (pictured below).
Here we can type into the search box “Web App Slow” which will list out your Top 5 Slowest Dependency Executions. When SQL may be an issue, the name field will have the word “database” within it.
Once this is seen, we can navigate to the SQL database and start looking at areas such as resource consumption (CPU, Memory), as well as seeing if we can optimize queries.
More verbose logging options such as Memory Dumps or .NET Profiler Traces which can be collected through Auto-Heal rules / manually can also lead to narrowing the issue down to SQL. These can be configured by navigating again to Diagnose and solve Problems -> Diagnostic Tools.
However, the initial recommendation of using the “Web App Slow” detector would be the quickest way to scope the issue, only using verbose logging as needed.
- Document on Collecting and Analyzing a Profiler Trace- App Service Diagnostics – Profiling an ASP.NET Web App on Azure App Service
- Document on Collecting and Analyzing a Memory Dump- How to get and Analyze a Memory Dump–Azure App Services – HTTP Stack and other fun things I support