Implementing workload management in an Azure Synapse dedicated SQL pool

How often have we seen a scenario where we have queries coming from a less important system hogging most of the resources and causing fewer resources to be available for business-critical queries, eventually resulting in dissatisfied customers/stakeholders? Wouldn’t it be nice to classify the queries based on their business needs and reserve and allocate resources accordingly?

Workload management in a Synapse dedicated SQL pool helps to classify the queries based on the user account used to run the query, the user role, and the application used and map them to resource classes. Resource classes are predefined resource pools with resource limits set as a percentage of the total number of resources. By defining rules that classify the queries and mapping them to resource classes, we could reserve resources based on the business needs and ensure that critical queries get the right amount of resources most...