RPC:Completed Event Class


Updated: December 4, 2015

Applies To: SQL Server 2016

The RPC:Completed event class indicates that a remote procedure call has been completed.

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
BinaryDataimageBinary value dependent on the event class captured in the trace.2Yes
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
CPUintAmount of CPU time used by the event. In microseconds beginning with SQL Server 2012. In milliseconds in earlier versions.18Yes
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
DurationbigintAmount of time taken by the event. In microseconds beginning with SQL Server 2008 R2. In milliseconds in earlier versions.13Yes
EndTimedatetimeTime at which the remote procedure call ended.15Yes
ErrorintError number of a given event.




EventClassintType of event = 10.27No
EventSequenceintSequence 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
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 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.41Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
NTUserNamenvarcharWindows user name.6Yes
ObjectNamenvarcharName of the object being referenced.34Yes
ReadsbigintNumber of page reads issued by the remote procedure call.16Yes
RequestIDintID of the request containing the statement.49Yes
RowCountsbigintNumber of rows in the RPC batch.48Yes
ServerNamenvarcharName of the instance of SQL Server being traced.26
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 of the remote procedure call.1Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes
WritesbigintNumber of page writes issued by the remote procedure call.17Yes
XactSequencebigintToken that describes the current transaction.50Yes

sp_trace_setevent (Transact-SQL)

Community Additions