Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance
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.
Audit Logout Event Class Data Columns Data column name Data type Description Column ID Filterable ApplicationName nvarchar Name 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. 10 Yes ClientProcessID int ID 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. 9 Yes CPU int Amount of CPU time (in milliseconds) used by the user during their connection. 18 Yes DatabaseID int ID 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. 3 Yes DatabaseName nvarchar Name of the database in which the user statement is running. 35 Yes Duration bigint Amount of time since the user logged in (approximately). 13 Yes EndTime datetime End time of the logout. 15 Yes EventClass int Type of event = 15. 27 No EventSequence int The sequence of a given event within the request. 51 No EventSubClass int Type of connection used by the login. 1 = Nonpooled, 2 = Pooled. 21 Yes HostName nvarchar Name 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. 8 Yes IsSystem int Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user. 60 Yes LoginName nvarchar Name of the login of the user (either the SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username). 11 Yes LoginSid image Security 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. 41 Yes NTDomainName nvarchar Windows domain to which the user belongs. 7 Yes NTUserName nvarchar Windows user name. 6 Yes Reads bigint Number of logical read I/Os issued by the user during the connection. 16 Yes RequestID int ID of the request containing the statement. 49 Yes ServerName nvarchar Name of the instance of SQL Server being traced. 26 SessionLoginName Nvarchar Login 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. 64 Yes SPID int ID of the session on which the event occurred. 12 Yes StartTime datetime StartTime of the related Audit Login event, if available. 14 Yes Success int 1 = 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. 23 Yes Writes bigint Number of logical write I/Os issued by the user during the connection. 17 Yes GroupID int ID of the workload group where the SQL Trace event fires. 66 Yes See Alsosp_trace_setevent (Transact-SQL)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4