Degree of Parallelism (7.0 Insert) Event Class

 

Applies To: SQL Server 2016

The Degree of Parallelism (7.0 Insert) event class occurs each time SQL Server executes a SELECT, INSERT, UPDATE, or DELETE statement.

When this event class is included in a trace, the amount of entailed overhead may significantly impede performance if these events occur frequently. To minimize overhead incurred, limit use of this event class to traces that briefly monitor specific problems.

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
BinaryDataimageNumber of CPUs used to complete the process based on the following values:

0x00000000, indicates a serial plan running in serial.

0x01000000, indicates a parallel plan running in serial.

>= 0x02000000 indicates a parallel plan running in parallel.
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 database statement 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 in which the user statement is running.35Yes
Event ClassintType of Event = 28.27No
EventSequenceintSequence of a given event within the request.51No
EventSubClassintIndicates the statement executed, based on the following values:

1=Select

2=Insert

3=Update

4=Delete
21No
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 DataintThe amount of "workspace memory" in kilobytes that the query has been granted to perform operations involving hashing, sorts or create index operations. The memory will be acquired during execution as needed.25Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60Yes
LoginNamenvarcharName of the login of the user (either the SQL Server security login or the 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.41Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
NTUserNamenvarcharWindows user name.6Yes
RequestIDintRequest identification that initiated the full-text query.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
TransactionIDbigintSystem-assigned ID of the transaction.4Yes

sp_trace_setevent (Transact-SQL)
INSERT (Transact-SQL)

Community Additions

ADD
Show: