diff --git a/data-explorer/kusto/management/materialized-views/materialized-views-limitations.md b/data-explorer/kusto/management/materialized-views/materialized-views-limitations.md
index dbd6b39c07..d08c0a4c4d 100644
--- a/data-explorer/kusto/management/materialized-views/materialized-views-limitations.md
+++ b/data-explorer/kusto/management/materialized-views/materialized-views-limitations.md
@@ -3,7 +3,7 @@ title:  Materialized views limitations
 description: This article describes materialized views limitations.
 ms.reviewer: yifats
 ms.topic: reference
-ms.date: 01/29/2025
+ms.date: 06/03/2026
 ---
 
 # Materialized views limitations and known issues
@@ -23,6 +23,7 @@ ms.date: 01/29/2025
 * The source table of a materialized view can't be a table with a [restricted view access policy](../restricted-view-access-policy.md).
 * A materialized view can't be created on top of another materialized view, unless the first materialized view is of type `take_any(*)` aggregation. See [materialized view over materialized view](materialized-view-overview.md#materialized-view-over-materialized-view).
 * Materialized views can't be defined over [external tables](../../query/schema-entities/external-tables.md).
+* Materialized views cannot be queried with [cursors](../../query/database-cursor.md)
 
 > [!WARNING]
 >
diff --git a/data-explorer/kusto/management/show-data-operations.md b/data-explorer/kusto/management/show-data-operations.md
index a95f942d24..6692b7f234 100644
--- a/data-explorer/kusto/management/show-data-operations.md
+++ b/data-explorer/kusto/management/show-data-operations.md
@@ -3,7 +3,7 @@ title: .show data operations
 description: Learn how to use the `.show data operations` command to return data operations that reached a final state. 
 ms.reviewer: vrozov
 ms.topic: reference
-ms.date: 08/22/2024
+ms.date: 06/03/2026
 ---
 # .show data operations command
 
@@ -37,7 +37,7 @@ This command returns a table with the following columns:
 |Database |`string`|The database name.|
 |Table |`string`|The table name.|
 |ClientActivityId |`string`|The operation client activity ID.|
-|OperationKind |`string`| One of `BatchIngest`, `SetOrAppend`, `RowStoreSeal`, `MaterializedView`, `QueryAcceleration`, and `UpdatePolicy`.|
+|OperationKind |`string`| See [Operation Kinds](#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.|
@@ -47,6 +47,20 @@ This command returns a table with the following columns:
 |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](data-ingestion/ingest-into-command.md)) or through managed ingestion |
+| `DataUpdate` | Ingestion resulting from [.update](update-table-command.md) command |
+| `SetOrAppend` | Ingestion through one of the [ingest through query commands](data-ingestion/ingest-from-query.md) |
+| `RowStoreSeal` | Sealing of row store [streaming ingestion](/azure/data-explorer/ingest-data-streaming) |
+| `MaterializedView` | Materialization of records by [Materialized view](materialized-views/materialized-view-overview.md) |
+| `QueryAcceleration` | Ingestion of external table records for [query acceleration](query-acceleration-policy.md) |
+| `UpdatePolicy` | Ingestion due to [update policy](update-policy.md) processing records |
+
 ## Example
 
 The following example returns information about `UpdatePolicy`, `BatchIngest`, and `SetOrAppend` operations.