You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-explorer/delete-data.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Azure Data Explorer supports various delete scenarios described in this article.
15
15
16
16
## Delete using retention policy
17
17
18
-
Azure Data Explorer automatically deletes data based on the [retention policy](/azure/kusto/management/retentionpolicy). This is the most efficient and hassle-free method of deleting data. Set the retention policy at the database or table level.
18
+
Azure Data Explorer automatically deletes data based on the [retention policy](/azure/kusto/management/retentionpolicy). This method is the most efficient and hassle-free way of deleting data. Set the retention policy at the database or table level.
19
19
20
20
Consider a database or table that is set for 90 days of retention. If only 60 days of data are needed, delete the older data as follows:
21
21
@@ -50,5 +50,5 @@ You can delete all rows in a table or just a specific extent.
50
50
> [!NOTE]
51
51
> Purge allows you to delete personal data from the device or service and can be used to support your obligations under the GDPR. If you're looking for general information about GDPR, see the [GDPR section of the Service Trust portal](https://servicetrust.microsoft.com/ViewPage/GDPRGetStarted).
52
52
53
-
[Data purge](/azure/kusto/management/data-purge) can be used for deleting individuals rows. Deletion is *not* immediate and requires significant system resources. Therefore, it is only advised for compliance scenarios.
53
+
[Data purge](/azure/kusto/management/data-purge) can be used for deleting individuals rows. Deletion isn't immediate and requires significant system resources. As such, it's only advised for compliance scenarios.
0 commit comments