SP:Recompile Event Class
The SP:Recompile event class indicates that a stored procedure, trigger, or user-defined function has been recompiled. In SQL Server 2005 and later, recompilations reported by this event class occur at the statement level, whereas those in SQL Server 2000 occurred at the batch level.
In SQL Server 2005 and later, the preferred way to trace statement-level recompilations is to use the SQL:StmtRecompile event class. Starting in SQL Server 2005, the SP:Recompile event class is deprecated. For more information, see SQL:StmtRecompile Event Class and "Recompiling Execution Plans" in Execution Plan Caching and Reuse.
Data column name
Name of the client application that created the connection to an instance of Microsoft SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program.
ID assigned by the host computer to the process where the client application is running. This data column is populated if the client provides the process ID.
ID of the database in which the stored procedure is running. Determine the value for a database by using the DB_ID function.
Name of the database in which the stored procedure is running.
Type of event = 37.
The sequence of a given event within the request.
Type of event subclass. Indicates the reason for recompilation.
1 = Schema Changed
2 = Statistics Changed
3 = Recompile DNR
4 = Set Option Changed
5 = Temp Table Changed
6 = Remote Rowset Changed
7 = For Browse Perms Changed
8 = Query Notification Environment Changed
9 = MPI View Changed
10 = Cursor Options Changed
11 = With Recompile Option
ID of the workload group where the SQL Trace event fires.
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.
Ending offset of the statement within the stored procedure or batch that caused recompilation. Ending offset is -1 if the statement is the last statement in its batch.
Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.
Name of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username).
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.
The nesting level of the stored procedure.
Windows domain to which the user belongs.
Windows user name.
System-assigned ID of the stored procedure.
Name of the object that triggered the recompile.
Value that represents the type of object involved in the event. For more information, see ObjectType Trace Event Column.
Starting offset of the statement within the stored procedure or batch that caused recompilation.
ID of the request containing the statement.
Name of the instance of SQL Server being traced.
Login 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.
ID of the session on which the event occurred.
64-bit hash based on the text of an ad hoc query or the database and object ID of an SQL object. This value can be passed to sys.dm_exec_sql_text to retrieve the associated SQL text.
Time at which the event started, if available.
Text of the Transact-SQL statement that caused a statement-level recompilation. Note that this data column was not populated in SQL Server 2000, but is populated in SQL Server 2005 and later.
System-assigned ID of the transaction.
Token used to describe the current transaction.