QN:Parameter Table Event Class

New: 14 April 2006

The QN:Parameter table event reports information about the operations required to create, keep reference counts for, and drop the internal tables that store parameter information. This event also reports the internal activity to reset the usage count for a parameter table.

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 database statement 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 = 200.

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:

  • Table created
    Indicates a parameter table has been created in the database.
  • Table drop attempt
    Indicates that the database has attempted to automatically drop an unused parameter table to free resources.
  • Table drop attempt failed
    Indicates that the database tried to drop an unused parameter table and failed. The Database Engine will automatically reschedule deletion of the parameter table to free up resources.
  • Table dropped
    Indicates that the database successfully dropped a parameter table.
  • Table pinned
    Indicates that the parameter table is marked for current usage by internal processing.
  • Table unpinned
    Indicates that the parameter table has been unpinned. Internal processing has finished using the table.
  • Number of users incremented
    Indicates that the number of query notification subscriptions that reference a parameter table has increased.
  • Number of users decremented
    Indicates that the number of query notification subscriptions that reference a parameter table has decreased.
  • LRU counter reset
    Indicates that the usage count for the parameter table has been reset.
  • Cleanup task started
    Indicates when cleanup for all subscriptions in this parameter table has started. This occurs when the database starts up or when a table underlying the subscriptions of this parameter table is dropped.
  • Cleanup task finished
    Indicates when cleanup for all subscriptions in this parameter table has finished.

21

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. 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

1

Yes

Community Additions

ADD
Show: