Skip to content

Commit 37a1ec5

Browse files
authored
Update sys-dm-workload-management-workload-group-stats-transact-sql.md
A customer was unclear on how to interpret the count in total_shared_resource_requests. Updated the description to better explain the count.
1 parent 5ac6cc3 commit 37a1ec5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/relational-databases/system-dynamic-management-views/sys-dm-workload-management-workload-group-stats-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Returns workload group statistics and the effective values of the workload group
2727
|name|**sysname**|Name of the workload group.||
2828
|statistics_start_time|**datetime**|Time that statistics collection began for the workload group. The value is either when the workload group was created or when instance is paused or scaled.||
2929
|total_request_count|**bigint**|Cumulative count of completed requests in the workload group.||
30-
|total_shared_resource_reqeusts|**bigint**|Cumulative count of completed requests in the workload group that used resources from the shared pool.||
30+
|total_shared_resource_requests|**bigint**|Cumulative count of completed requests in the workload group that go beyond the reserved resources for the workload group and use resources from the shared pool. When the workload group does not have a MinResourcePercentage set, the requests will always be using shared resources and do not register in this count.||
3131
|total_queued_request_count|**bigint**|Cumulative count of requests queued after the max_concurrency limit was reached.||
3232
|total_request_execution_timeouts|**bigint**|Cumulative count of requests in the workload group that timed out before completion based on the query_execution_timeout_sec setting.||
3333
|effective_min_percentage_resource|**tinyint**|The effective min_percentage_resource setting allowed considering the service level and the workload group settings. The effective min_percentage_resource can be adjusted higher on lower service levels. For example, on DW100c, the lowest min_percentage_resource allowable is 25%. The min_percentage_resource is adjusted to 0% if the value cannot be granted at the service level. For example, min_percentage_resource set to 10% at DW6000c, would have an effective_min_percentage_resource of 0% when scaled down to DW100c.||

0 commit comments

Comments
 (0)