Skip to content

Commit 405194d

Browse files
committed
Documented table delete experience
1 parent 8ff2f11 commit 405194d

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

articles/azure-monitor/logs/create-custom-table.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: adi.biran
77
ms.service: azure-monitor
88
ms.custom: devx-track-azurepowershell
99
ms.topic: how-to
10-
ms.date: 10/23/2023
10+
ms.date: 01/28/2024
1111
# Customer intent: As a Log Analytics workspace administrator, I want to manage table schemas and be able create a table with a custom schema to store logs from an Azure or non-Azure data source.
1212
---
1313

@@ -151,12 +151,11 @@ Use the [Tables - Update PATCH API](/rest/api/loganalytics/tables/update) to cre
151151

152152
## Delete a table
153153

154-
You can delete any table in your Log Analytics workspace that's not an [Azure table](../logs/manage-logs-tables.md#table-type-and-schema).
155-
156-
> [!NOTE]
157-
> - Deleting a restored table doesn't delete the data in the source table.
158-
> - Azure tables that are part of a solution can be removed from workspace when [deleting the solution](/cli/azure/monitor/log-analytics/solution#az-monitor-log-analytics-solution-delete). The data remains in workspace for the duration of the retention policy defined for the tables. If the [solution is re-created](/cli/azure/monitor/log-analytics/solution#az-monitor-log-analytics-solution-create) in the workspace, these tables become visible again.
159-
> - In both cases, data retention and archive charges will continue to apply to the data associated with these tables.
154+
There are several types of tables in Log Analytics and the delete experience is different for each:
155+
- [Azure table](../logs/manage-logs-tables.md#table-type-and-schema) -- Can't be deleted. Tables that are part of a solution are removed from workspace when [deleting the solution](/cli/azure/monitor/log-analytics/solution#az-monitor-log-analytics-solution-delete), but data remains in workspace for the duration of the retention policy defined for the tables, or if not exist, for the duration of the retention policy defined in workspace. If the [solution is re-created](/cli/azure/monitor/log-analytics/solution#az-monitor-log-analytics-solution-create) in the workspace, these tables and previously ingested data become visible again. To avoid charges, define [retention policy for tables in solutions](https://learn.microsoft.com/rest/api/loganalytics/tables/update) to minimum (4-days) before deleting the solution.
156+
- [Restored table](./restore.md) (table_RST) -- Deletes the hot cache provisioned for the restore, but source table data isn't deleted.
157+
- [Search results table](./search-jobs.md) (table_SRCH) -- Deletes the table and data immediately and permanently.
158+
- [Custom log table](./create-custom-table.md#create-a-custom-table) (table_CL) -- Deletes the table definition immediately, but data remains in workspace for the duration of the retention policy defined for the table, or workspace. The retention policy for table is removed in 14-days and workspace retention governs. If custom log table is created with the same name and schema, the table and previously ingested data become visible again. To avoid charges and remove data from table, define [retention policy for table](https://learn.microsoft.com/rest/api/loganalytics/tables/update) to minimum (4-days) before deleting the table.
160159

161160
# [Portal](#tab/azure-portal-2)
162161

0 commit comments

Comments
 (0)