Category: SQLServerPedia Syndication

The event_file target is an asynchronous consumer for Extended Events. This target stores the received payload in a proprietary binary format. Because of this, one needs to use the sys.fn_xe_file_target_read_file function. This article will discuss this function and show how to use it in its simplest form.

Having just completed several segments on the metadata for deployed sessions, it is time to bring all of that information together and see how it can be used – by showing how to backup deployed sessions.

SET operations in extended events are the extra configurations that can be made to various components. As an example, a target can be configured with certain properties via the use of a SET operation when creating the Extended Event Session. The best way to see the SET Options and Metadata, is by seeing it in action.

In the case of the final core component, Targets, the exploration into the metadata can be a little awkward. At least at first. Read on to see how to explore the deployed session target metadata at a preliminary level.

The Extended Events GUI provides a visual access to the Extended Events engine that can help to better understand the XEvents Engine and how a Session is built.

With the core concepts in place as a good foundation to Extended Events, we start pushing these things together to help with assembling a session in Extended Events.

Predicates are a significant component within the Extended Events Engine. This article discusses one of the pieces of the puzzle of predicates – comparison operators – also known as pred_compare.

Among the several core concepts of Extended Events is the concept of storing event payloads / data.

Working with databases, XML, and many software applications, it is not uncommon to deal with fixed schemas. In the database world, it is fairly fundamental to have some sort of schema. The schema represents the typing of the bit-strings that are being stored or presented. One might even call it the template.