Workload Importance for Azure SQL Data Warehouse is now generally available
Published date: 08 May, 2019
Running mixed workloads on your analytics solution is often a necessity to effectively and quickly execute business processes. In situations where resources are constrained, the capability to decide which workloads need to be executed first is critical, as it helps with overall solution cost management. For instance, executive dashboard reports may be more important than ad-hoc queries. Workload importance now enables this scenario. Requests with higher importance are guaranteed quicker access to resources, which helps meet predefined SLAs and ensures important requests are prioritised.
Workload classification concept
To define workload priority, various requests must be classified. Azure SQL Data Warehouse supports flexible classification policies that can be set for a SQL query, a database user, database role, Azure Active Directory login or Azure Active Directory group. Workload classification is achieved using the new CREATE WORKLOAD CLASSIFIER syntax.
Workload importance concept
Workload importance is established through classification. Importance influences a requestor’s access to system resources including memory, CPU, and IO and locks. A request can be assigned one of these five levels of importance: low, below_normal, normal, above_normal and high. If a request with above_normal importance is scheduled, it gets access to resources before a request with the default normal importance.
For more information on workload importance, see the Classification and Importance overview articles in the documentation. Take a look at the CREATE WORKLOAD CLASSIFIER doc as well.
https://azure.microsoft.com/en-au/blog/azure-sql-data-warehouse-releases-new-capabilities-for-performance-and-security/Read the announcement blog