Analyzing Database Wait Statistics Telemetry
APPLIES TO: Business Central 2022 release wave 1, version 20.0, and later
Note
Azure Active Directory is now Microsoft Entra ID. Learn more
The database performance can also be analyzed by checking the information at Database Wait Statistics. You can see how many queries got delayed because of different wait types along with their wait times. The wait types give you an idea about the resources or operations that are responsible for the slow performance.
For more information about wait statistics in optimizing database and application performance, see Database Wait Statistics in Dynamics 365 Business Central.
Note
The wait times aren't live. These statistics show the wait times for the queries which are completed from the time the database was started or when it was reset.
Database wait statistics snapshot taken
Occurs when you choose the Emit Telemetry icon on the Database Wait Statistics view in the client.
General dimensions
Dimension | Description or value |
---|---|
message | Database wait statistics snapshot taken: {snapshotId} |
severityLevel | 1 |
user_Id | The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. For more information, see Assign a telemetry ID to users. |
Custom dimensions
Dimension | Description or value |
---|---|
eventId | RT0025 |
snapshotId | Specifies the ID given to the snapshot. |
Common custom dimensions
The following table explains custom dimensions that are common to all database wait statistic traces.
Dimension | Description or value |
---|---|
aadTenantId | Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common. |
component | Dynamics 365 Business Central Server. |
componentVersion | Specifies the version number of the component that emits telemetry (see the component dimension.) |
environmentType | Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See Environment Types. |
telemetrySchemaVersion | Specifies the version of the Business Central telemetry schema. |
Database wait statistics snapshot entry
Occurs when a query has to wait because of a resource, queue, or external event in the client. It's the snapshot entry for each wait category.
General dimensions
Dimension | Description or value |
---|---|
message | Database wait statistics snapshot entry: {databaseWaitStatisticsCategory} |
severityLevel | 1 |
user_Id | The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. For more information, see Assign a telemetry ID to users. |
Custom dimensions
Dimension | Description or value |
---|---|
eventId | RT0026 |
snapshotId | Specifies the ID given to the snapshot. |
databaseMaxWaitTimeInMs | Specifies the maximum wait time in milliseconds for a specific wait category. |
databaseSignalWaitTimeInMs | Specifies the time difference between when the query was signaled to wait and when it starts to process. |
databaseStartedDuration | Specifies the date and time when the database was started. |
databaseWaitingTasksCount | Specifies the total number of waits for a wait category. |
databaseWaitStatisticsCategory | Specifies which type of wait a query is experiencing. |
databaseWaitTimeInMs | Specifies the total wait time for a wait category including the databaseSignalWaitTimeInMs. |
See common custom dimensions |
See also
Monitoring and Analyzing Telemetry
Enable Sending Telemetry to Application Insights
Performance for Developers
How to work with a performance problem
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for