Holds information about all requests currently or recently active in SQL Data Warehouse. It lists one row per request/query.
|Column Name||Data Type||Description||Range|
|request_id||nvarchar(32)||Key for this view. Unique numeric ID associated with the request.||Unique across all requests in the system.|
|session_id||nvarchar(32)||Unique numeric ID associated with the session in which this query was run. See sys.dm_pdw_exec_sessions (Transact-SQL).|
|status||nvarchar(32)||Current status of the request.||'Running', 'Suspended', 'Completed', 'Canceled', 'Failed'.|
|submit_time||datetime||Time at which the request was submitted for execution.||Valid datetime smaller or equal to the current time and start_time.|
|start_time||datetime||Time at which the request execution was started.||NULL for queued requests; otherwise, valid datetime smaller or equal to current time.|
|end_compile_time||datetime||Time at which the engine completed compiling the request.||NULL for requests that haven't been compiled yet; otherwise a valid datetime less than start_time and less than or equal to the current time.|
|end_time||datetime||Time at which the request execution completed, failed, or was canceled.||Null for queued or active requests; otherwise, a valid datetime smaller or equal to current time.|
|total_elapsed_time||int||Time elapsed in execution since the request was started, in milliseconds.||Between 0 and the difference between start_time and end_time.
If total_elapsed_time exceeds the maximum value for an integer, total_elapsed_time will continue to be the maximum value. This condition will generate the warning "The maximum value has been exceeded."
The maximum value in milliseconds is the same as 24.8 days.
|label||nvarchar(255)||Optional label string associated with some SELECT query statements.||Any string containing 'a-z','A-Z','0-9','_'.|
|error_id||nvarchar(36)||Unique ID of the error associated with the request, if any.||See sys.dm_pdw_errors (Transact-SQL); set to NULL if no error occurred.|
|database_id||int||Identifier of database used by explicit context (for example, USE DB_X).||See ID in sys.databases (Transact-SQL).|
|command||nvarchar(4000)||Holds the full text of the request as submitted by the user.||Any valid query or request text. Queries that are longer than 4000 bytes are truncated.|
|resource_class||nvarchar(20)||The resource class for this request. See related concurrency_slots_used in sys.dm_pdw_resource_waits (Transact-SQL). For more information on resource classes, see Resource classes & workload management||Static Resource Classes
Dynamic Resource Classes
|importance (Workload classification is available for preview on SQL Data Warehouse Gen2. Workload Management Classification and Importance preview is for builds with a release date of April 9th, 2019 or later. Users should avoid using builds earlier than this date for workload management testing. To determine if your build is workload management capable, run select @@version when connected to your SQL Data Warehouse instance.)||nvarchar(32)||The importance setting the request was submitted with. Requests with a lower importance will remain queued in suspended state, if higher importance requests are submitted. Requests with higher importance will execute before lower importance requests that were submitted earlier. For more information on importance, see Workload Importance.||NULL
For information about the maximum rows retained by this view, see the Metadata section in the Capacity limits topic.
Requires VIEW SERVER STATE permission.
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
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.
Send feedback about: