---
title: "sys.dm_exec_external_work (Transact-SQL) | Microsoft Docs"
ms.custom: ""
ms.date: 11/04/2019
ms.prod: sql
ms.prod_service: "database-engine, sql-data-warehouse, pdw"
ms.reviewer: ""
ms.technology: system-objects
ms.topic: "language-reference"
f1_keywords: 
  - "DM_EXEC_EXTERNAL_WORK"
  - "DM_EXEC_EXTERNAL_WORK_TSQL"
  - "SYS.DM_EXEC_EXTERNAL_WORK_TSQL"
dev_langs: 
  - "TSQL"
helpviewer_keywords: 
  - "sys.dm_exec_external_work management view"
  - "dm_exec_external_work management view"
  - "PolyBase,views"
  - "PolyBase"
ms.assetid: 7597d97b-1fde-4135-ac35-4af12968f300
author: stevestein
ms.author: sstein
monikerRange: ">=aps-pdw-2016||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
---
# sys.dm_exec_external_work (Transact-SQL)
[!INCLUDE[tsql-appliesto-ss2016-xxxx-asdw-pdw-md](../../includes/tsql-appliesto-ss2016-xxxx-asdw-pdw-md.md)]

  Returns information about the workload per worker, on each compute node.  
  
 Query sys.dm_exec_external_work to identify the work spun up to communicate with the external data source (e.g. Hadoop or external SQL Server).  
  
|Column Name|Data Type|Description|Range|  
|-----------------|---------------|-----------------|-----------|  
|execution_id|`nvarchar(32)`|Unique identifier for associated PolyBase query.|See *request_ID* in [sys.dm_exec_requests (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-requests-transact-sql.md).|  
|step_index|`int`|The request this worker is performing.|See *step_index* in  [sys.dm_exec_requests (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-requests-transact-sql.md).|  
|dms_step_index|`int`|Step in the DMS plan that this worker is executing.|See [sys.dm_exec_dms_workers (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-dms-workers-transact-sql.md).|  
|compute_node_id|`int`|The node the worker is running on.|See [sys.dm_exec_compute_nodes (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-compute-nodes-transact-sql.md).|  
|type|`nvarchar(60)`|The type of external work.|'File Split'|  
|work_id|`int`|ID of the actual split.|Greater than or equal to 0.|  
|input_name|`nvarchar(4000)`|Name of the input to be read|File name when using Hadoop.|  
|read_location|`bigint`|Offset or read location.|Offset of the file to read.|  
|bytes_processed|`bigint`|Total bytes allocated for processing data by this worker. This may not necessarily represent the total data being returned by the query |Greater than or equal to 0.|  
|length|`bigint`|Length of the split or HDFS block in case of Hadoop|User-definable. The default is 64M|  
|status|`nvarchar(32)`|Status of the worker|Pending, Processing, Done, Failed, Aborted|  
|start_time|`datetime`|Beginning of the work||  
|end_time|`datetime`|End of the work||  
|total_elapsed_time|`int`|Total time in milliseconds||
|compute_pool_id|`int`|Unique identifier for the pool.|

## See Also  
 [PolyBase troubleshooting with dynamic management views](https://msdn.microsoft.com/library/ce9078b7-a750-4f47-b23e-90b83b783d80)   
 [Dynamic Management Views and Functions (Transact-SQL)](~/relational-databases/system-dynamic-management-views/system-dynamic-management-views.md)   
 [Database Related Dynamic Management Views (Transact-SQL)](../../relational-databases/system-dynamic-management-views/database-related-dynamic-management-views-transact-sql.md)