QN:Dynamics Event Class

Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance

The QN:Dynamics event class reports information about the background activity that the Database Engine performs to support query notifications. Within the Database Engine, a background thread monitors subscription time-outs, pending subscriptions to be fired, and parameter table destruction.

QN:Dynamics Event Class Data Columns

Data column Type Description Column number Filterable
ApplicationName nvarchar The 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 The 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 The ID of the database specified by the USE database statement, or the ID of the default database if no USE databasestatement has been issued for a given instance. SQL Server Profiler displays the name of the database if the Server Name 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 The name of the database in which the user statement is running. 35 Yes
EventClass int Type of event = 202 27 No
EventSequence int Sequence number for this event. 51 No
EventSubClass nvarchar The type of event subclass, providing further information about each event class. This column may contain the following values:

Clock run started: Indicates that the background thread in the Database Engine that schedules expired parameter tables for cleanup has started.

Clock run finished: Indicates that the background thread in the Database Engine that schedules expired parameter tables for cleanup has finished.

Master cleanup task started: Indicates when cleanup (garbage collection) to remove expired query notification subscription data starts.

Master cleanup task finished: Indicates when cleanup (garbage collection) to remove expired query notification subscription data finishes.

Master cleanup task skipped: Indicates that the Database Engine did not perform cleanup (garbage collection) to remove expired query notification subscription data.
21 Yes
GroupID int ID of the workload group where the SQL Trace event fires. 66 Yes
HostName nvarchar The 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.

0 = user

1 = system
60 No
LoginName nvarchar The name of the login of the user (either SQL Server security login or the Windows login credentials in the form of DOMAIN\Username). 11 No
LoginSID image The 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 The Windows domain to which the user belongs. 7 Yes
NTUserName nvarchar The name of the user that owns the connection that generated this event. 6 Yes
RequestID int Identifier of the request that contains the statement. 49 Yes
ServerName nvarchar The name of the instance of SQL Server being traced. 26 No
SessionLoginName nvarchar Login name of the user that originated the session. For example, if an application connects to SQL Server using Login1 and executes 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 Time at which the event started, if available. 14 Yes
TextData ntext Returns an XML document containing information specific to this event. This document conforms to the XML schema available at the SQL Server Query Notification Profiler Event Schema page. 1 Yes