Overview
Storage table is an Azure NoSQL datastore that holds large volumes of structured, non-relational data. It stores data as entities, each with a partition key, row key, and a set of properties, making it well-suited for structured logs, diagnostics data, and application state that does not require complex relational queries.
Business value
Managing Storage table entities from Turbo360 gives you direct query and purge capabilities without leaving the platform. Instead of writing custom scripts or switching to Azure Storage Explorer, you can query entities using OData filter syntax, inspect their contents, and purge data that no longer needs to be retained, all from within your Business Application context.
How it works
Once a Storage table is associated with a Business Application, you can query its entities from the Queries tab using OData filter expressions. Entities matching your query are returned in a paginated results view showing standard fields (PartitionKey, RowKey, Timestamp) alongside any custom entity properties. Purge operations let you remove entities older than a specified time threshold using the Purge entities inline task or via Automated Tasks.
Permissions
Access to Storage table actions is controlled through RBAC when adding a role to a Business Application.
| Permission | Description |
|---|---|
| Read | View entities and monitoring configuration. |
| Manage | Configure monitoring rules. |
| Purge | Delete entities via inline task or automated tasks. |
Operations
Turbo360 lets you query and purge Storage table entities directly, removing the need to switch to Azure Storage Explorer or write custom scripts.
Query entities
Querying lets you retrieve and inspect entities from a Storage table using OData filter syntax, directly from the Queries tab.
- Navigate to your Storage table resource within your Business Application.
- Select the Queries tab.
- Enter an OData filter expression in the query field, for example
PartitionKey eq 'key' and RowKey ne '100'. - Click Run.
Results are displayed in a paginated table showing Odata.etag, PartitionKey, RowKey, Timestamp, and any custom entity properties. Results are restricted to the first 1000 records for performance. Use Save to save frequently used queries for reuse.
Query syntax reference
Queries follow OData filter syntax: field1 eq "value" and ( field2 eq "value" or field3 gt value ).
| Data type | Syntax |
|---|---|
| String | Use single quotes around the value, e.g. PartitionKey eq 'myKey'. Replace any single quote inside the value with two consecutive single quotes. |
| DateTime | Use datetime'dd/MM/yyyy HH:mm:ss' or ISO 8601 format, e.g. datetime'25/09/2020 16:30:00'. |
| Guid | Use guid'Your-128-bit-Guid-value'. |
| Boolean | Use true or false without quotes. |
Inline task
- Purge entities: quickly purge entities from the table by specifying a Created at or before time offset (Days, Hours, Minutes, and Seconds) and an optional configuration name (if Save configuration is enabled). Use this when you need to clear old or expired records from a table on demand without setting up a full automated task.
Task status can be viewed from Automated tasks > Task history.
Navigate to the Automated tasks section in Turbo360 to create a task with a more detailed configuration, schedule tasks to run at a specific time, or automate the task to run on the specified hours, days, and more.
Monitoring
Storage table supports query monitoring, configured under Storage table > Monitoring.
Query monitoring
Tracks query results against a defined threshold or condition. Use this when you need to be alerted if entity counts in the table exceed an expected range or meet a specific condition.
- Navigate to Storage table > Monitoring.
- Configure the query and threshold conditions.
- Click Save.
Troubleshooting
- Purge entities option is unavailable
Cause: The role applied to the Business Application lacks the Purge permission for Storage table.
Fix: Confirm the role includes the Purge permission for Storage table, then retry. - Query returns no results despite data being present
Cause: The OData filter expression does not match any entities, or the PartitionKey or RowKey values entered are incorrect.
Fix: Verify the PartitionKey and RowKey values against the data in Azure, then re-run the query. - Query results are truncated at 1000 records
Cause: Results are limited to the first 1000 records for performance.
Fix: Narrow the query using more specific PartitionKey or RowKey filter conditions to reduce the result set. - Monitoring rule does not trigger despite matching entities
Cause: The configured threshold or condition does not match the current entity state, or the rule was saved before the first monitoring cycle completed.
Fix: Review the threshold and query conditions, then allow one full monitoring cycle to pass before re-checking. - Purge completes but entities are still visible in query results
Cause: The query results view may not have refreshed after the purge completed.
Fix: Re-run the query after the purge task finishes to confirm the entities have been removed.