We have been using Azure SQL successfully with low data amounts for some time. Now when we have seen moderate increase in data storage volumes we are experiencing very long query times. What is weird is that querying dm_exec_query_stats shows that the worker/cpu time for queries is very low (roughly 0 seconds) but the elapsed time is long (can be over 30 seconds).
We have upgraded our pricing tier to 100 DTU's after which our resource consumption for all categories is only < 10% of available resources. The execution plans look decent and given that cpu times are so low this shouldn't be an issue.
I have also checked wait times which has yielded no significant results. The wait times for individual queries show just a few milliseconds of wait times and the only significant wait type is SOS_WORK_DISPATCHER which doesn't ring a bell - or exist in Microsoft documentation.
Both the web application and sql server consuming the data are both in Azure West Europe and considering that we have not seen considerable IO amounts it shouldn't be a problem.
Does anyone have an idea what could be causing this or what is SOS_WORK_DISPATCHER
6Related questions 3 SQL Azure slow performance 1 Adding WHERE adds 20+ seconds to SQL Azure query 9 Azure SQL wait operation timed out Related questions 3 SQL Azure slow performance 1 Adding WHERE adds 20+ seconds to SQL Azure query 9 Azure SQL wait operation timed out 8 sql azure time consuming query 2 Understanding Azure SQL Performance 9 Azure SQL Database - Slow 0 Azure SQL Performance 0 SQL Execution in Azure taking a very long time 3 Azure SQL database time issue 0 SQL lag statement taking too long to run on Azure SQLDB Load 7 more related questions Show fewer related questions
Reset to default
