audit-database-principal-impersonation-event-class.md

title	description	author	ms.author	ms.date	ms.service	ms.subservice	ms.topic	helpviewer_keywords	monikerRange
Audit Database Principal Impersonation Event Class	Audit Database Principal Impersonation Event Class	WilliamDAssafMSFT	wiassaf	06/03/2020	sql	supportability	reference	Audit Database Principal Impersonation event class	=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

Audit Database Principal Impersonation Event Class

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance] The Audit Database Principal Impersonation event class occurs when an impersonation occurs within the database scope, such as EXECUTE AS <user> or SETUSER.

Audit Database Principal Impersonation 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 [!INCLUDEmsCoName] [!INCLUDEssNoVersion]. This column is populated with the values passed by the application rather than the displayed name of the program.	10	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. [!INCLUDEssSqlProfiler] 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
DBUserName	nvarchar	[!INCLUDEssNoVersion] user name of the client.	40	Yes
EventSequence	int	Sequence of a given event within the request.	51	No
EventSubClass	int	Type of event subclass.	21	Yes
HostName	nvarchar	Name of the computer on which the client is running. This data column is populated if the client provides the host name. 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 [!INCLUDEssNoVersion] security login or the [!INCLUDEmsCoName] 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
ObjectName	nvarchar	Name of the object being referenced.	34	Yes
ObjectType	int	Value representing the type of the object involved in the event. This value corresponds to the type column in the sys.objects catalog view. For values, see ObjectType Trace Event Column.	28	Yes
Permissions	bigint	Integer value representing the type of permissions checked. 1 = SELECT ALL 2 = UPDATE ALL 4 = REFERENCES ALL 8 = INSERT 16 = DELETE 32 = EXECUTE (procedures only)	19	Yes
RequestID	int	ID of the request containing the statement.	49	Yes
RoleName	nvarchar	Name of an application role being enabled.	38	Yes
ServerName	nvarchar	Name of the instance of [!INCLUDEssNoVersion] being traced.	26	No
SessionLoginName	nvarchar	Login name of the user who originated the session. For example, if you connect to [!INCLUDEssNoVersion] using Login1 and execute a statement as Login2, SessionLoginName shows Login1 and LoginName shows Login2. This column displays both [!INCLUDEssNoVersion] 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. For example, a value of 1 means success of a permissions check and a value of 0 means a failure of that check.	23	Yes
TextData	ntext	Text value dependent on the event class captured in the trace.	1	Yes
TransactionID	bigint	System-assigned ID of the transaction.	4	Yes
XactSequence	bigint	Token used to describe the current transaction.	50	Yes

See Also

sp_trace_setevent (Transact-SQL)
EXECUTE AS Clause (Transact-SQL)
SETUSER (Transact-SQL)