CursorUnprepare Event Class

 

Applies To: SQL Server 2016

The CursorUnprepare event class provides information about cursor unprepare events that occur in application programming interface (API) cursors. Cursor unprepare events occur when the Microsoft Database Engine discards an execution plan.

Include the CursorUnprepare event class in traces that record the performance of cursors. When the CursorUnprepare event class is included in a trace, the amount of overhead incurred depends on how frequently cursors are used against the database during the trace. If cursors are used extensively, the trace can significantly impede performance.

Data column nameData typeDescriptionColumn IDFilterable
ApplicationNamenvarcharName 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 with the displayed name of the program.10Yes
ClientProcessIDintID assigned by the host computer to the process where the client application is running. This data column is populated if the client provides the client process ID.9Yes
DatabaseIDintID of the database specified by the USE statement or the default database if no USE 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.3Yes
DatabaseNamenvarcharName of the database in which the user statement is running.35Yes
EventClassintType of event recorded = 77.27No
EventSequenceintBatch sequence of the CursorUnprepare event class.51No
GroupIDintID of the workload group where the SQL Trace event fires.66Yes
HandleIntIdentifies the prepared handle that is being unprepared.33Yes
HostNamenvarcharName 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.8Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60Yes
LoginNamenvarcharName of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username).11Yes
LoginSidimageSecurity identifier (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.41Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
NTUserNamenvarcharWindows user name.6Yes
RequestIDintRequest identification that unprepared the cursor.49Yes
ServerNamenvarcharName of the instance of SQL Server being traced.26No
SessionLoginNamenvarcharLogin name of the user that 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.64Yes
SPIDintID of the session on which the event occurred.12Yes
StartTimedatetimeTime at which the event started, if available.14Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes
XactSequencebigintToken that describes the current transaction.50Yes

sp_trace_setevent (Transact-SQL)

Community Additions

ADD
Show: