Resource Governance - Resource Pools - Control CPU, physical IO, memory, priority, run-time cap, max request, concurrency, request timeout..
- Ability to manage workloads effectively
- Enables to specify limits on the amount of CPU, physical IO and memory
- User-Defined Resource Pools
a. Memory size
b. Memory cap
d. Maximum requests
e. Grant time-out
h. Run-time cap
This is available for public preview as announced at Ignite this November, 2019.
Please add these features. Without these features a small number of users are likely to sink performance ... and are.
Absolutely important, if you want run your enterprise DW for hundreds of users and multiple teams with variety of workload.
This is a critical requirement for any enterprise data warehouse workload. SQL Server has it so why does SQL DW not have it? The resource class/slots model is hugely complicated and after you put in the effort to learn it, you realize it's basically useless since it only governs some of the memory allocations, no control on CPU or IO.
Sankalp Mandovara commented
Very essential to manage the workloads.
Kaushik Periwal commented
Very much needed feature, is this on roadmap?
Rithesh Vijayakrishnan commented
Here's a reference from Redshift: http://docs.aws.amazon.com/redshift/latest/dg/cm-c-defining-query-queues.html
Agree with this idea.. We need better control in controlling the user accounts that are requesting requests in SQL-DW.. Please guide if there is any existing options to put the threshold cap.