The Spotlight Diagnostic Server (by default) uses Extended Events to collect data from monitored Azure SQL Managed instances and SQL Server instances (above SQL Server 2008). The data is used by:
- SQL Server | Workload Analysis Drilldown
- SQL Server | Wait Events Drilldown
- Deadlock checks: SQL Server | SQL Activity Drilldown, Locks - Deadlocks Alarm.
Use this screen to either request that the Spotlight Diagnostic Server not use Extended Events to collect data from monitored Azure SQL Managed instances and SQL Server instances or to customize the Spotlight Diagnostic Server use of Extended Events via advanced options.
Open this screen from the Spotlight Client
- Click Configure | Diagnostic server.
- Select Configure the use of Extended Events.
Select the Diagnostic Server
For federated Spotlight Diagnostic Server you will be prompted to select the Spotlight Diagnostic Server to configure. Each Spotlight Diagnostic Server is independently configured in its use of Extended Events.
Configure the use of Extended Events.
Deselect the use of Extended Events
If you deselect the use of Extended Events then the Spotlight Diagnostic Server will stop collecting data for the SQL Server | Workload Analysis Drilldown and SQL Server | Wait Events Drilldown. This will not show up immediately on the user interface as the drilldowns will continue to show historical data till no data is available.
If you deselect the use of Extended Events then the Spotlight Diagnostic Server will use SQL Server Trace to collect data for deadlock checks.
Select to use Extended Events
This is the default setting. If you select to use Extended Events (following a period of time when the use of Extended Events was deselected) the SQL Server | Workload Analysis Drilldown and SQL Server | Wait Events Drilldown may take a few minutes to repopulate with data.
Advanced Options controlling the Event Session properties are available only when the use of Extended Events is selected. For more information than is documented here refer to the Microsoft Web Site: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-event-session-transact-sql.
The maximum amount of memory to allocate to the session for event buffering. Measured in Kilobytes.
Event Retention Mode
How to manage event loss from the session.
Allow Single Event Loss
A single event is only dropped when all the event buffers are full. Losing a single event when event buffers are full allows for acceptable SQL Server performance characteristics, while minimizing the loss of data in the processed event stream.
Allow Multiple Event Loss
Full event buffers containing multiple events can be lost from the session. The number of events lost is dependent upon the memory size allocated to the session, the partitioning of the memory, and the size of the events in the buffer. This option minimizes performance impact on the server when event buffers are quickly filled, but large numbers of events can be lost from the session.
Max Dispatch Latency
The length of time (in seconds) that events will be buffered in memory before being dispatched to event session targets. The minimum latency value is 1 second. However, 0 can be used to specify INFINITE latency.
Memory Partition Mode
The location where event buffers are created.
A single set of buffers are created within the SQL Server instance and Azure SQL Managed Instance.
A set of buffers are created for each NUMA node.
A set of buffers are created for each CPU.
The starting minimum duration to use to collect for Wait Events and Workload Analysis.