![]() Modify the deadlock monitoring session to use a file-based target (known as an event_file target). Reading from the event_file target is only supported in Business Central Cumulative Update 3 and later. ![]() If you want to use the default ring_buffer target, then no further action is required. ![]() So, if your setup has a high volume of database traffic, you might have to change the SQL Server to write deadlock events to an event_file target as described the steps that follow. Using the event_file target can eliminate potential overloads in high volume situations. An important difference between the ring_buffer target and event_file target is that the ring_buffer target has a storage size limitation of 5MB, while the event_file target provides a much greater storage capacity. You have the option to also store the events to a file on the SQL Server, called an event_file target, and configure the Business Central Server to read from this file instead of the ring_buffer target. When the Business Central Server is notified about the deadlock, it reads data from the target ring_buffer target. ![]() Configure where to store deadlock eventsīy default, SQL Server uses an in-memory data structure called a ring_buffer target to store deadlock events. The next time a client session is established with the database, a session for monitoring the Business Central database appears under Management, Extended Events.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |