| title | Audit Login Failed event class | |
|---|---|---|
| description | Audit Login Failed event class | |
| author | WilliamDAssafMSFT | |
| ms.author | wiassaf | |
| ms.date | 02/25/2026 | |
| ms.service | sql | |
| ms.subservice | supportability | |
| ms.topic | reference | |
| helpviewer_keywords |
|
|
| monikerRange | >=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDE SQL Server Azure SQL Managed Instance]
The Audit Login Failed event class indicates that a user tried to sign in to [!INCLUDE msCoName] [!INCLUDE ssNoVersion] and failed. Events in this class are fired by new connections or by connections that are reused from a connection pool.
This event class is part of SQL Trace, which is deprecated. For Azure SQL Database, use auditing for Azure SQL Database instead.
| Data column name | Data type | Description | Column ID | Filterable |
|---|---|---|---|---|
| ApplicationName | nvarchar | Name of the client application that created the connection to an instance of [!INCLUDE ssNoVersion]. This column is populated with the values passed by the application instead of 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 |
| 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. [!INCLUDE ssSqlProfiler] 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 |
| Error | int | Error number of a given event. Often this is the error number stored in the sys.messages catalog view. | 31 | Yes |
| EventClass | int | Type of event = 20. | 27 | No |
| EventSequence | int | The sequence of a given event within the request. | 51 | No |
| 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 [!INCLUDE ssNoVersion] security login or the Windows login credentials in the form of DOMAIN\username). | 11 | Yes |
| NTDomainName | nvarchar | Windows domain to which the user belongs. | 7 | Yes |
| NTUserName | nvarchar | Windows user name. | 6 | Yes |
| RequestID | int | The ID of the request containing the statement. | 49 | Yes |
| ServerName | nvarchar | Name of the instance of [!INCLUDE ssNoVersion] being traced. | 26 | No |
| SessionLoginName | nvarchar | Login name of the user who originated the session. For example, if you connect to [!INCLUDE ssNoVersion] using Login1 and execute a statement as Login2, SessionLoginName shows Login1 and LoginName shows Login2. This column displays both [!INCLUDE ssNoVersion] and Windows logins. | 64 | Yes |
| SPID | int | ID of the session on which the event occurred. | 12 | Yes |
| StartTime | datetime | Time at which the event started, if available. | 14 | Yes |
| Success | int | 1 = success. 0 = failure. This event always shows failure. | 23 | Yes |
| TextData | ntext | Text value dependent on the event class captured in the trace. | 1 | Yes |