Specifies the ID of the session that was involved by the deadlock. Specifies the version of that was involved in the deadlock. Specifies the name of the extension that was involved in the deadlock. Specifies the AppID of the extension that was involved in the deadlock. Specifies the environment type for the tenant, such as Production, Sandbox, Trial. Specifies the name of the tenant environment. Specifies the version number of the component that emits telemetry (see the component dimension.) Specifies the display name of the Business Central company. For a list of the client types, see ClientType Option Type. Specifies the type of client that executed the SQL Statement, such as Background or Web. Specifies the type of the AL object that ran the transaction that was victim of the deadlock, such as a page or report. Specifies the name of the AL object that ran the transaction that victim of the deadlock. Specifies the name of the AL object that ran the transaction that was victim of the deadlock. Specifies the ID of the AL object that ran the transaction that was victim of the deadlock. For on-premises, if you aren't using Microsoft Entra authentication, this value is common. Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For more information, see Assign a telemetry ID to users. From the user card, you can use user_Id to identify the user who triggered this telemetry event. For more information, see Configuring Business Central Server. For more information, see Database lock trace telemetry.įor Business Central on-premises, you must turn on the EnableDeadlockMonitoring setting of the Business Central Server instance to collect the telemetry. For more information, see Monitoring SQL Database Deadlocks. Enable SQL database deadlock monitoring on a sandbox or on-premises environment.For further monitoring and troubleshooting, this telemetry is complimented by other features like:.In these cases, both will be stored in the telemetry resource as different deadlock events. In some deadlock problems, the process that is the victim and the process that succeeds will change by chance.Let's you identify who was the victim in deadlock situations.Makes you aware that there are deadlocks happening.The system terminates and rolls back one of the sessions (known as the deadlock victim), then emits a telemetry signal.Īs a partner or developer, this telemetry provides several benefits: A deadlock occurs when two or more processes block each other because each has locked a database resource. Deadlocks can prevent users from completing tasks in the Business Central client. The database deadlock telemetry gathers information about deadlocks that happen. Azure Active Directory is now Microsoft Entra ID.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |