Note
Access to this page requires authorization. You can try signing in or .
Access to this page requires authorization. You can try .
.show data operations command
Switch services using the Version drop-down list. Learn more about navigation.
Applies to: ✅ Microsoft Fabric ✅ Azure Data Explorer
Returns a table with data operations that reached a final state. Data operations are available for 30 days from when they ran.
Any operation that results in new extents (data shards) added to the system is considered a data operation.
Permissions
You must have Database Admin or Database Monitor permissions to see any data operations invoked on your database.
Any user can see their own data operations.
For more information, see Kusto role-based access control.
Syntax
.show data operations
Learn more about syntax conventions.
Returns
This command returns a table with the following columns:
| Output parameter | Type | Description |
|---|---|---|
| Timestamp | datetime |
The time when the operation reached its final state. |
| Database | string |
The database name. |
| Table | string |
The table name. |
| ClientActivityId | string |
The operation client activity ID. |
| OperationKind | string |
See Operation Kinds |
| OriginalSize | long |
The original size of the ingested data. |
| ExtentSize | long |
The extent size. |
| RowCount | long |
The number of rows in the extent. |
| ExtentCount | int |
The number of extents. |
| TotalCpu | timespan |
The total CPU time used by the data operation. |
| Duration | timespan |
The duration of the operation. |
| Principal | string |
The identity that initiated the data operation. |
| Properties | dynamic |
Additional information about the data operation. |
Operation Kinds
The operation kind column can take one of the following values:
| Operation Kind | Description |
|---|---|
BatchIngest |
Ingestion through one of the batch ingestion command (e.g. .ingest into) or through managed ingestion |
DataUpdate |
Ingestion resulting from .update command |
SetOrAppend |
Ingestion through one of the ingest through query commands |
RowStoreSeal |
Sealing of row store streaming ingestion |
MaterializedView |
Materialization of records by Materialized view |
QueryAcceleration |
Ingestion of external table records for query acceleration |
UpdatePolicy |
Ingestion due to update policy processing records |
Example
The following example returns information about UpdatePolicy, BatchIngest, and SetOrAppend operations.
.show data operations
Output
| Timestamp | Database | Table | ClientActivityId | OperationKind | OriginalSize | ExtentSize | RowCount | ExtentCount | TotalCpu | Duration | Principal | Properties |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024-07-18 15:21:10.5432134 | TestLogs | UTResults | DM.IngestionExecutor;abcd1234-1234-1234-abcd-1234abcdce;1 | UpdatePolicy | 100,829 | 75,578 | 279 | 1 | 00:00:00.2656250 | 00:00:28.9101535 | aadapp=xxx | {"SourceTable": "UTLogs"} |
| 2024-07-18 15:21:12.9481819 | TestLogs | UTLogs | DM.IngestionExecutor;abcd1234-1234-1234-abcd-1234abcdce;1 | BatchIngest | 1,045,027,298 | 123,067,947 | 1,688,705 | 2 | 00:00:22.9843750 | 00:00:29.9745733 | aadapp=xxx | {"Format": "Csv","NumberOfInputStreams":2} |
| 2024-07-18 15:21:16.1095441 | KustoAuto | IncidentKustoGPTSummary | cdef12345-6789-ghij-0123-klmn45678 | SetOrAppend | 1,420 | 3,190 | 1 | 1 | 00:00:00.0156250 | 00:00:00.0638211 | aaduser=xxx |
Feedback
Was this page helpful?