Documentation Index

Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt

Use this file to discover all available pages before exploring further.

Storage management

  • 3 minute(s) read
Prev Next

Overview

Storage management in Business Activity Monitoring (BAM) covers three operations available on the Storage details tab of the Configuration screen: updating the SQL database and storage account connection strings, configuring the purge batch size for outdated transactions, and patching the BAM database when business process changes are not reflected in the tracking data. These operations are available only in the Custom Logging type (Push Model).

Business value

Keeping connection strings current ensures BAM continues writing tracking data to the correct backend storage. The purge batch size setting lets you tune cleanup performance for your data volume. Database patching resolves sync gaps where modified business process configurations have not yet propagated to the BAM SQL database, preventing tracking discrepancies.

How it works

BAM stores tracking data — including business process names, transaction names, and stage data — in the SQL database configured at deployment. The storage account holds archived message payloads.

When you update connection strings, BAM immediately begins writing to the new targets. The purge batch size controls how many records are deleted per purge cycle, letting you balance cleanup throughput against database load. When business process configurations are modified (e.g. a transaction is renamed or a stage is added), the BAM database may not reflect those changes immediately. The Patch database operation forces a sync of the latest configurations.

Note:

Updating connection strings and patching the database are available only in the Custom Logging type (Push Model).

Steps

Use the following steps to update storage configuration and patch the database. Navigate to Business Activity Monitoring > Settings (gear icon) > Configuration > Storage details to get started.

Update connection strings and purge batch size

Updating the connection strings redirects BAM data tracking to a different SQL database or storage account.

  1. Navigate to Business Activity Monitoring > Settings > Configuration > Storage details.
  2. Click the Edit dropdown and select Storage Account or SQL Database to update the respective connection string.
  3. Set the Purge batch size to the number of records you want deleted per purge cycle.
  4. Save your changes.

Patch the database

Patching forces the BAM database to sync the latest business process configurations when modified processes are not reflected in tracked data.

  1. Navigate to Business Activity Monitoring > Settings > Configuration > Storage details.
  2. Click Patch database.

The BAM database updates with the latest business process, transaction, and stage configurations.

Purging blob data

Blob data in the storage account accumulates over time as messages are archived. To delete outdated blob data, implement Azure Lifecycle Management rules on the storage account.

Requirements:

  • Only StorageV2 (General Purpose v2) storage accounts support Azure Lifecycle Management.
  • Use sl360<customerid> as the blob prefix to target only BAM data within the container.

To configure lifecycle management:

  1. In the Azure portal, open the target storage account.
  2. Go to Data Management > Lifecycle Management in the resource menu.
  3. Set the blob container name including the customer ID as the blob prefix.
  4. Create the appropriate lifecycle rule to expire blobs beyond the desired retention period.

Troubleshooting

  1. Business process changes are not reflected in tracked data
    Cause: The BAM database has not synced the latest business process configuration.
    Fix: Navigate to Configuration > Storage details and click Patch database.

  2. Purge is running slowly or timing out
    Cause: The purge batch size may be too large for the current database performance tier.
    Fix: Reduce the purge batch size in Configuration > Storage details and monitor performance.

  3. Connection string update does not take effect
    Cause: The new connection string may contain a typo or incorrect credentials.
    Fix: Verify the connection string format, credentials, and network access (firewall rules) for the target SQL database or storage account.

  4. Blob data is not being purged despite lifecycle rules being configured
    Cause: The blob prefix in the lifecycle rule does not match the sl360<customerid> pattern, or the storage account type does not support lifecycle management.
    Fix: Confirm the storage account is StorageV2 (General Purpose v2) and that the blob prefix matches exactly.

Related articles