Audit Logout Event Class
TOC
Collapse the table of content
Expand the table of content

Audit Logout Event Class

 

The Audit Logout event class indicates that a user has logged out of (logged off) Microsoft SQL Server. Events in this class are fired by new connections or by connections that are reused from a connection pool.

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
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 (in milliseconds) used by the user during their connection.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 since the user logged in (approximately).13Yes
EndTimedatetimeEnd time of the logout.15Yes
EventClassintType of event = 15.27No
EventSequenceintThe sequence of a given event within the request.51No
EventSubClassintType of connection used by the login. 1 = Nonpooled, 2 = Pooled.21Yes
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 the 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
ReadsbigintNumber of logical read I/Os issued by the user during the connection.16Yes
RequestIDintID of the request containing the statement.49Yes
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
Successint1 = success. 0 = failure. For example, a value of 1 indicates success of a permissions check and a value of 0 indicates failure of that check.23Yes
WritesbigintNumber of logical write I/Os issued by the user during the connection.17Yes
GroupIDintID of the workload group where the SQL Trace event fires.66Yes

sp_trace_setevent (Transact-SQL)

Show:
© 2016 Microsoft