CursorPrepare Event Class

 

Applies To: SQL Server 2016

The CursorPrepare event class describes cursor prepare events that occur in application programming interface (API) cursors. Cursor prepare events occur when the Microsoft Database Engine compiles a SELECT statement associated with a cursor into an execution plan but does not create the cursor.

Include the CursorPrepare event class in traces that are recording the performance of cursors. When the CursorPrepare event class is included in a trace, the amount of overhead incurred will depend on how frequently cursors are used against the database during the trace. If cursors are used extensively, the trace may 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 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 process ID is provided by the client.9Yes
DatabaseIDintID 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. 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 = 70.27No
EventSequenceintSequence of CursorPrepare event class in batch.51No
GroupIDintID of the workload group where the SQL Trace event fires.66Yes
HandleintHandle of the event class.33Yes
HostNamenvarcharName 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.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 Windows login credentials in the form of DOMAIN\username).11Yes
LoginSidimageSecurity 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.41Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7No
NTUserNamenvarcharWindows user name.6Yes
RequestIDintRequest identification that prepared the cursor.49Yes
ServerNamenvarcharName of the instance of SQL Server being traced.26No
SessionLoginNamenvarcharLogin name of the user who 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, when available.14Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes
XactSequencebigintToken used to describe the current transaction.50Yes

Extended Events
sp_trace_setevent (Transact-SQL)
Cursors

Community Additions

ADD
Show: