Overview
When Business Activity Monitoring (BAM) provisions an environment, it creates a set of Azure SQL Database tables and assigns background worker roles to your account. This reference describes what data is stored in each table, how background jobs handle the processing pipeline, and who can perform the initial deployment.
Business value
Knowing which tables BAM creates lets your database administrators anticipate storage requirements, apply appropriate access controls, and diagnose data issues by querying the correct tables. Understanding background job provisioning clarifies the account-level permissions required before deployment begins.
How it works
When you initiate BAM environment deployment, Turbo360 provisions a set of tables in your Azure SQL Database and assigns background worker roles to your BAM account. These tables hold all tracking state — from transaction runs and stage results to exception alerts and user assignments.
SQL Database tables
BAM creates the following tables in your connected Azure SQL Database:
| Table | What it stores |
|---|---|
| BlobUrl | The URL of each blob containing a tracked message body and message header. |
| BusinessProcessName | The tracking name and friendly name of every business process created in BAM. |
| Configuration | Transaction configuration for all business processes. |
| ExceptionAlert | Exceptions logged against transaction instances. |
| FavouriteTransactionInstance | Transaction instances marked as favourites in BAM. |
| StageInstance | Each tracked run of a stage within a transaction. |
| StageInstanceEvent | Each run of a stage that was not tracked — typically caused by misconfigured event sources such as an incorrect tracking name. |
| StageName | The tracking name and friendly name of every stage across all business processes. |
| TransactionInstance | Each tracked run of a transaction. |
| TransactionName | The tracking name and friendly name of every transaction across all business processes. |
| TransactionsWithExceptionAlert | Transaction IDs for which at least one transaction instance has logged an exception. |
| AssignedInstance | Transaction instances that have been assigned to a user. |
Background jobs
After deployment, Turbo360 assigns worker roles to your BAM account. These background jobs handle the processing pipeline that moves tracked data from the event source through to the SQL Database for display in the platform.
Only the Account Owner of the Turbo360 account can perform the initial deployment that provisions these worker roles.
Troubleshooting
-
Tracked data is not appearing in the platform after deployment.
Cause: Background worker roles may not have been provisioned correctly, or the Azure Function does not have network access to the SQL Database.
Fix: Verify that the Azure Function's IP is allowed in the SQL Server firewall settings. Re-initiate deployment if worker roles were not assigned. -
StageInstanceEvent table contains unexpected entries.
Cause: An event source is sending data with an incorrect tracking name that does not match any configured stage.
Fix: Review the tracking names configured in the event source and compare them against the stage tracking names in BAM. Correct any mismatches in the event source configuration. -
Deployment cannot be initiated.
Cause: The user attempting deployment is not the Account Owner.
Fix: Ask the Account Owner to perform the initial deployment from their Turbo360 account. -
Tables are missing from the SQL Database after deployment.
Cause: Deployment failed partway through due to a connection string error or firewall restriction.
Fix: Review the connection strings in the BAM Storage details section. Confirm firewall rules allow the Azure Function to access the database, then re-initiate deployment. -
FavouriteTransactionInstance table is empty despite marking favorites.
Cause: The BAM platform user session may not have committed the favorite action, or the background job has not yet processed the event.
Fix: Re-mark the transaction instance as a favourite and wait for the next background job cycle to process the update.