You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/relational-databases/system-catalog-views/sys-workload-management-workload-classifier-details-transact-sql.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,4 +31,4 @@ Requires VIEW SERVER STATE permission.
31
31
32
32
## Next steps
33
33
34
-
For a list of all the catalog views for SQL Data Warehouse and Parallel Data Warehouse, see [SQL Data Warehouse and Parallel Data Warehouse Catalog Views](../../relational-databases/system-catalog-views/sql-data-warehouse-and-parallel-data-warehouse-catalog-views.md). To create a workload classifier, see [CREATE WORKLOAD CLASSIFIER](../../t-sql/statements/create-workload-classifier-transact-sql.md). For more information on workload classification, see SQL Data Warehouse [Workload Classification](/azure/sql-data-warehouse/sql-data-warehouse-workload-classification) and [Workload Importance](/azure/sql-data-warehouse/sql-data-warehouse-workload-classification)
34
+
For a list of all the catalog views for SQL Data Warehouse and Parallel Data Warehouse, see [SQL Data Warehouse and Parallel Data Warehouse Catalog Views](../../relational-databases/system-catalog-views/sql-data-warehouse-and-parallel-data-warehouse-catalog-views.md). To create a workload classifier, see [CREATE WORKLOAD CLASSIFIER](../../t-sql/statements/create-workload-classifier-transact-sql.md). For more information on workload classification, see SQL Data Warehouse [Workload Classification](/azure/sql-data-warehouse/sql-data-warehouse-workload-classification) and [Workload Importance](/azure/sql-data-warehouse/sql-data-warehouse-workload-classification)
|cap_percentage_resource|**tinyint**|Hard cap on the resource percentage allocation for all requests in the workload group. Limits the maximum resources allocated to the specified level. The allowed range for value is from 1 through 100.||
30
30
|request_min_resource_grant_percent|**decimal(5,2)**|Specifies the minimum amount of resources allocated to a request. The allowed range for value is from 0.75 to 100.||
31
31
|request_max_resource_grant_percent |**decimal(5,2)**|Specifies the maximum amount of resources allocated to a request.||
32
-
|query_execution_timeout_sec|**int**|The amount of execution time, in seconds, allowed before the query is cancelled. Queries cannot be cancelled once they have reached the return phase of execution. query_execution_timeout_sec does not include time spent queued.||
32
+
|query_execution_timeout_sec|**int**|The amount of execution time, in seconds, allowed before the query is cancelled. Queries cannot be cancelled once they have reached the return phase of execution. query_execution_timeout_sec does not include time spent queued.|
33
33
|query_wait_timeout_sec|**int**|INTERNAL||
34
-
35
34
|create_time|**datetime**|Time the workload group was created. Is not nullable.||
36
35
modify_time|**datetime**|Time the workload group was last modified. Is not nullable.||
|importance|**nvarchar(128)**|The Importance setting the request executed at. This is the relative importance of a request in this workload group and across workload groups for shared resources. Importance specified in the classifier overrides the workload group importance setting.</br>Applies to: Azure SQL Data Warehouse|NULL</br>low</br>below_normal</br>normal (default)</br>above_normal</br>high|
38
38
|group_name|**sysname**|For requests utilizing resources, group_name is the name of the workload group the request is running under. If the request does not utilize resources, group_name is null.</br>Applies to: Azure SQL Data Warehouse|
39
39
|classifier_name|**sysname**|For requests utilizing resources, group_name is the name of the workload group the request is running under. If the request does not utilize resources, group_name is null.||
40
-
|resource_allocation_percentage|**decimal(5,2)|The percentage amount of resources allocated to the request.</br>Applies to: Azure SQL Data Warehouse|
40
+
|resource_allocation_percentage|**decimal(5,2)**|The percentage amount of resources allocated to the request.</br>Applies to: Azure SQL Data Warehouse|
41
41
|result_set_cache|**bit**|Details whether a completed query was a result cache hit (1) or not (0). </br>Applies to: Azure SQL Data Warehouse|0,1|
42
42
||||
43
43
44
-
For information about the maximum rows retained by this view, see the Metadata section in the [Capacity limits](/azure/sql-data-warehouse/sql-data-warehouse-service-capacity-limits#metadata) topic.
44
+
For information about the maximum rows retained by this view, see the Metadata section in the [Capacity limits](/azure/sql-data-warehouse/sql-data-warehouse-service-capacity-limits#metadata) topic.
sys.dm_pdw_exec_requests doesn't filter query results according to database-specific permissions. Logins with VIEW SERVER STATE permission can obtain results query results for all databases
53
53
54
54
>[!WARNING]
55
-
>An attacker can use sys.dm_pdw_exec_requests to retrieve information about specific database objects by simply having VIEW SERVER STATE permission and by not having a database-specific permission.
55
+
>An attacker can use sys.dm_pdw_exec_requests to retrieve information about specific database objects by simply having VIEW SERVER STATE permission and by not having database-specific permission.
56
56
57
57
## See Also
58
58
59
-
[SQL Data Warehouse and Parallel Data Warehouse Dynamic Management Views (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sql-and-parallel-data-warehouse-dynamic-management-views.md)
59
+
[SQL Data Warehouse and Parallel Data Warehouse Dynamic Management Views (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sql-and-parallel-data-warehouse-dynamic-management-views.md)
Copy file name to clipboardExpand all lines: docs/t-sql/statements/create-workload-classifier-transact-sql.md
+14-15Lines changed: 14 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,26 +44,25 @@ WITH
44
44
[ [ , ] START_TIME = ‘HH:MM’ ]
45
45
[ [ , ] END_TIME = ‘HH:MM’ ]
46
46
47
-
[ [ , ] IMPORTANCE = { LOW | BELOW NORMAL | NORMAL | ABOVE NORMAL | HIGH }]) [;]
48
-
47
+
[ [ , ] IMPORTANCE = { LOW | BELOW NORMAL | NORMAL | ABOVE NORMAL | HIGH }])
48
+
[;]
49
49
```
50
50
51
51
## Arguments
52
52
53
53
*classifier_name*
54
54
Specifies the name by which the workload classifier is identified. classifier_name is a sysname. It can be up to 128 characters long and must be unique within the instance.
55
55
56
-
*WORKLOAD_GROUP* = *'name'*
57
-
When the conditions are met by the classifier rules, name maps the request to a workload group. name is a sysname. It can be up to 128 characters long and must be a valid workload group name at the time of classifier creation.
58
-
59
-
Available workload groups can be found in [sys.workload_management_workload_groups](/sql/relational-databases/system-catalog-views/sys-workload-management-workload-groups-transact-sql?view=azure-sqldw-latest
60
-
) catalog view.
56
+
*WORKLOAD_GROUP* = *'name'*
57
+
When the conditions are met by the classifier rules, name maps the request to a workload group. name is a sysname. It can be up to 128 characters long and must be a valid workload group name at the time of classifier creation.
61
58
62
-
*MEMBERNAME* ='security_account'*
63
-
This is the security account being added to the role. Security_account is a sysname, with no default. Security_account can be a database user, database role, Azure Active Directory login, or Azure Active Directory group.
59
+
Available workload groups can be found in [sys.workload_management_workload_groups](/sql/relational-databases/system-catalog-views/sys-workload-management-workload-groups-transact-sql?view=azure-sqldw-latest) catalog view.
64
60
65
-
*WLM_LABEL*
66
-
Specifies the label value that a request can be classified against. label is an optional parameter of type nvarchar(255). Use the OPTION (LABEL) [link TDB] in the request match the classifier configuration.
61
+
*MEMBERNAME* ='security_account'*
62
+
This is the security account being added to the role. Security_account is a sysname, with no default. Security_account can be a database user, database role, Azure Active Directory login, or Azure Active Directory group.
63
+
64
+
*WLM_LABEL*
65
+
Specifies the label value that a request can be classified against. Label is an optional parameter of type nvarchar(255). Use the OPTION (LABEL) [link TDB] in the request to match the classifier configuration.
67
66
68
67
Example:
69
68
@@ -78,7 +77,7 @@ SELECT COUNT(*)
78
77
OPTION (LABEL ='fact_loads')
79
78
```
80
79
81
-
*WLM_CONTEXT*
80
+
*WLM_CONTEXT*
82
81
Specifies the session context value that a request can be classified against. context is an optional parameter of type nvarchar(255). Use the sys.sp_set_session_context with the variable name equal to ‘wlm_context’ prior to submitting a request to set the session context.
83
82
84
83
Example:
@@ -99,7 +98,7 @@ SELECT COUNT(*) FROM stg.daily_sales_load
Specifies the start_time and end_time that a request can be classified against. Both start_time and end_time are of the HH:MM format in UTC time zone. Start_time and end_time must be specified together.
104
103
105
104
Example:
@@ -112,7 +111,7 @@ CREATE WORKLOAD CLASSIFIER wcELTLoads WITH
112
111
,END_TIME ='02:00' )
113
112
```
114
113
115
-
*IMPORTANCE* = { LOW | BELOW_NORMAL | NORMAL | ABOVE_NORMAL | HIGH }
114
+
*IMPORTANCE* = { LOW | BELOW_NORMAL | NORMAL | ABOVE_NORMAL | HIGH }
116
115
Specifies the relative importance of a request. Importance is one of the following:
117
116
118
117
- LOW
@@ -151,7 +150,7 @@ CREATE WORKLOAD CLASSIFIER classiferB WITH
151
150
152
151
The user ‘userloginA’ is configured for both classifiers. If userloginA runs a query with a label equal to ‘salesreport’ between 6PM and 7AM UTC, the request will be classified to the wgDashboards workload group with HIGH importance. The expectation may be to classify the request to wgUserQueries with LOW importance for off-hours reporting, but the precedence of WLM_LABEL is higher than START_TIME/END_TIME. In this case, you can add START_TIME/END_TIME to classiferA.
153
152
154
-
For more information see, [workload classification](/azure/sql-data-warehouse/sql-data-warehouse-workload-classification#classification-precedence)
153
+
For more information see, [workload classification](/azure/sql-data-warehouse/sql-data-warehouse-workload-classification#classification-precedence).
0 commit comments