The full Script, without warranty and support. changeset_7d6bec6f-eced-4cd9-8b40-9f9c528fd991ĭELETE $StorageUri/$TableName(PartitionKey='APARTITIONKEY',RowKey='AROWKEY') HTTP/1.1Īccept: application/json odata=minimalmetadata
#Azure tables query with timestamp plus#
DELETE) plus the URL of the StorageAccount including the name of the table and the partitionkey and rowkey as parameters.Įxample of a body with a single DELETE request: -batch_8360b73e-53ce-4ab8-8de8-3894086bd697Ĭontent-type: multipart/mixed boundary=changeset_7d6bec6f-eced-4cd9-8b40-9f9c528fd991 The HTTP Post request must contain a body, that includes the activity (e.g. Deleting entities in a batchīy using entity group transactions, you can significant speed up the process as you can delete up to 100 rows in a single HTTP POST request. That's because Azure table storage has some performance restrictions. You will realize that the performance is not very good if you have to delete thousands of entities. To delete an entity on an Azure storage table, you have to call an HTTP DELETE request including the PartitionKey and RowKey of the entity to delete. To get the next 1000 rows, you have to call an HTTP GET request including the NextPartitionKey and NextRowKey: "$($StorageUri)/$($TableName)()?$SASToken&`$filter=$($Query)&NextPartitionKey=$($nextPartkey)&NextRowKey=$($nextRowKey)" Deleting entities If your filter affects more than 1000 rows, the HTTP GET request returns a Request-Header with the next PartitionKey and RowKey ( x-ms-continuation-NextPartitionKey and x-ms-continuation-NextRowKey). You have to be aware, that you only get the first 1000 Rows. Note: To prevent PowerShell to interpret $filter as a PowerShell variable, you have to escape the dollar sign like `$filter The script does an HTTP GET request on "$($StorageUri)/$($TableName)()?$SASToken&`$filter=$($Query)" Query the existing entitiesĪs first step, we need to get the existing items as we need the PartitionKey and RowKey for every item.īased on the Documentation, we can use the $filter option to return only entities that matches with this filter. The PowerShell function returns the number of deleted rows. Check out for more details.Įxample: "PartitionKey eq 'part1' and Timestamp ge datetime'T13:49:49.000Z' and Timestamp lt datetime'T13:49:49.000Z'" Return value Make sure you grant delete rights on the Azure Table. You can use "Azure Storage Explorer" or the Azure Portal to generate a SAS Token. SASToken is used to authenticate on the Storage Account.
TableName specifies the table you want to use SASToken StorageUri is the URL of your StorageAccount like TableName The PowerShell function requires some parameters: Remove-AzureTableEntities -SASToken "sv=&se=T13%3A38%3A38Z&sp=raud&sig=vCQ4%2Bg0rt5YGGI8bFGv5tW0o5s2KMl31NuXwIGjJ3vo%3D&tn=test" -StorageUri "" -TableName "TEST" -Query "PartitionKey eq 'lookup' and Timestamp ge datetime'T13:49:49.000Z' and Timestamp lt datetime'T13:49:49.000Z'" Make sure you have a Backup! and double check your queries !!! Example Note: Recovering data takes much more time than deleting. if the query returns more than 1000 rows, use pagination to get all rows.100 rows to delete them within a batch request In short, the PowerShell function does the following logic: This example Script provides a way to use " Entity Group Transactions" and " Paging" to speed things up. Deleting massive amounts of Azure table entities based on a query can be a time- consuming task.
0 kommentar(er)
