![]() ![]() select map_value Keyword from sys.dm_xe_map_valuesĪctions that are intended for a specific set of events cannot bind to unknown events.Īn action bound to an event is invoked synchronously on the thread that fired the event. You can use the following query to obtain keyword information. Therefore, events in the Debug channel may change or be removed in future versions of SQL Server without notice.Ī keyword is application specific and enables a finer-grained grouping of related events, which makes it easier for you to specify and retrieve an event that you want to use in a session. The schemas and data that the events return may change or become invalid in future versions of SQL Server. They describe program operation and are typically used in performance investigations.ĭebug events are used solely by developers to diagnose a problem for debugging.Įvents in the Debug channel return internal implementation-specific state data. An example of an operational event is when a printer is added or removed from a system.Īnalytic events are published in high volume. They can be used to trigger tools or tasks based on the problem or occurrence. Operational events are used for analyzing and diagnosing a problem or occurrence. These events are either well-documented or have a message associated with them that tells the reader what to do to rectify the problem. An example of an admin event is when an application fails to connect to a printer. The events that are found in the admin channels indicate a problem with a well-defined solution that an administrator can act on. TermĪdmin events are primarily targeted to the end users, administrators, and support. These channels are described in the following table. Using these properties supports the integration of Extended Events with ETW and its tools.Ī channel identifies the audience for an event. Two event properties are used for categorization, channel and keyword. Event CategorizationĮxtended Events uses an event categorization model similar to Event Tracing for Windows (ETW). However, an event target does not have to consume all the data that is provided. An event of a specific type must always provide its data in exactly the same order that is specified in the schema. This schema is composed of event columns with well defined types. These actions can either be synchronous or asynchronous.Īn event does not have any knowledge of the actions that may be triggered in response to the event firing.Ī set of events in a package cannot change after the package is registered with Extended Events.Īll events have a versioned schema which defines their contents. An event firing carries with it the fact that the point of interest was reached, and state information from the time the event was fired.Įvents can be used solely for tracing purposes or for triggering actions. A module can be an executable or a dynamic link library.Įvents are monitoring points of interest in the execution path of a program, such as SQL Server. The following illustration shows the objects that can exist in packages, which are contained in a module. For more information, see SQL Server Extended Events Sessions. Objects from different packages can be mixed in an event session. For more information, see sys.dm_xe_packages (Transact-SQL).Ī package can contain any or all of the following objects, which are discussed in greater detail later in this topic: Packages are identified by a name, a GUID, and the binary module that contains the package. None of the objects in the package are available through the Extended Events data definition language (DDL). The SecAudit package is used by SQL Server Audit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |