Tag: Extended Events

The premise of the article today is to get a little exposure to some of the internals that may cause a bit of curiosity for you. I will share a means to expose some of the settings/stages/steps of various internal processes. These are the sorts of things you may have heard about, but without Extended Events, you might have to dig harder and further to find them.

The predicate order is critical. Having the wrong order can result in not trapping the desired events. I cover the critical nature of predicates in the aforementioned article. At least in principle. Today, I want to reinforce the topic through the use of examples.

This article will show how to implement an XEvent Session that employs the use of the event_counter target that is used for counting events. IN addition, you will be shown how to parse the data and get some meaningful counts of event occurrences in your SQL Server Instances.

In this article I show how to use and configure the histogram target. In addition, I explain how to get to the data trapped into this target. Lastly, I demonstrate how to find the pertinent information for the target configurations.

In this article I will be taking you into the world of the pair_matching target. The pair_matching target should connote that this target works on matching like events into a single pair. Very much like a pair of socks would contain two parts, one for each foot or side of the body, the pair_matching target creates pairs of events that go together.

In this article I will be taking you into the world of the pair_matching target. The pair_matching target should connote that this target works on matching like events into a single pair. Very much like a pair of socks would contain two parts, one for each foot or side of the body, the pair_matching target creates pairs of events that go together.

When adding a Target to a session, a configurable setting may or may not be obviously available for use with the Target. In and of itself, this can be mildly frustrating if the wrong settings are tried with the wrong Target. More frustrating is that some settings are required. While the required setting may be logically deduced, it does not always work out that way.

In this article, I introduce the topic of reading session data from memory along with some of the pitfalls and some words of caution.

In this article, I am going to address some better practices for Reading Event_file targets attached to an XEvent Session.

There needs to be a more efficient means of grabbing the file without having to know the location. Knowing the session name should be adequate enough to parse the payload data from the target. This is exactly what I am going to show in this article – retrieving the file and path based strictly on the name of the session.