Showplan XML Event Class


Applies To: SQL Server 2016

The Showplan XML event class occurs when Microsoft SQL Server executes an SQL statement. Include the Showplan XML event class to identify the Showplan operators. This event class stores each event as a well-defined XML document.

When the Showplan XML event class is included in a trace, the amount of overhead will significantly impede performance. Showplan XML stores a query plan that is created when the query is optimized. To minimize the overhead incurred, limit use of this event class to traces that monitor specific problems for brief periods of time.

The Showplan XML documents have a schema associated with them. This schema can be found at the Microsoft Web Site, or as part of your Microsoft SQL Server installation.

Data column nameData typeDescriptionColumn IDFilterable
ApplicationNamenvarcharName of the client application that created the connection to an instance of SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program.10Yes
BinaryDataimageEstimated cost of the query.2No
ClientProcessIDintID assigned by the host computer to the process where the client application is running. This data column is populated if the client process ID is provided by the client.9Yes
DatabaseIDintID of the database specified by the USE database statement or the default database if no USE databasestatement has been issued for a given instance. SQL Server Profiler displays the name of the database if the ServerName data column is captured in the trace and the server is available. Determine the value for a database by using the DB_ID function.3Yes
DatabaseNamenvarcharName of the database.35No
Event ClassintType of Event = 122.27No
EventSequenceintThe sequence of a given event within the request.51No
GroupIDintID of the workload group where the SQL Trace event fires.66Yes
HostNamenvarcharName of the computer on which the client is running. This data column is populated if the host name is provided by the client. To determine the host name, use the HOST_NAME function.8Yes
Integer DataintegerEstimated number of rows returned.25Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60Yes
LineNumberintDisplays the number of the line containing the error.5Yes
LoginNamenvarcharName of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username).11Yes
LoginSIDimageSecurity identification number (SID) of the logged-in user. You can find this information in the sys.server_principals catalog view. Each SID is unique for each login in the server.41No
NestLevelintInteger representing the data returned by @@NESTLEVEL.29Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
ObjectIDintSystem-assigned ID of the object.22Yes
ObjectNamenvarcharName of the object being referenced.34Yes
ObjectTypeintValue representing the type of the object involved in the event. This value corresponds to the type column in the sys.objects catalog view. For values, see ObjectType Trace Event Column.28Yes
RequestIDintID of the request containing the statement.49Yes
ServerNamenvarcharName of the instance of SQL Server being traced.26No
SessionLoginNamenvarcharLogin name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute a statement as Login2, SessionLoginName shows Login1 and LoginName shows Login2. This column displays both SQL Server and Windows logins.64Yes
SPIDintID of the session on which the event occurred.12Yes
StartTimedatetimeTime at which the event started, if available.14Yes
TextDatantextText value dependent on the event class captured in the trace.1Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes
XactSequencebigintToken used to describe the current transaction.50Yes

Extended Events
sp_trace_setevent (Transact-SQL)
Showplan Logical and Physical Operators Reference

Community Additions