CLR Event Category


Applies To: SQL Server 2016

The CLR event category includes event classes that are produced by the execution of .NET Framework common language runtime (CLR) objects inside SQL Server.

The Assembly Load event class occurs when a request to load an assembly is executed.

Include the Assembly Load event class in traces where you want to monitor assembly loads. This can be useful when troubleshooting a query that uses common language runtime (CLR), when troubleshooting a slow running server that is running CLR queries, or when monitoring a server to gather user, database, success, or other information about assembly loads.

Data column nameData typeDescriptionColumn IDFilterable
ApplicationNamenvarcharThe name of the application that requested the load.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 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
EventSequenceintSequence of a given event within the request.51No
GroupIDintID of the workload group where the SQL Trace event fires.66Yes
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
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
ObjectIDintAssembly ID.22Yes
ObjectNamenvarcharFully qualified name of the assembly.34Yes
RequestIDintID of the request containing the statement.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
SuccessintIndicates whether the assembly load succeeded (1) or failed (0).23Yes
TextDatantext"Assembly Load Succeeded" if the load succeeds; otherwise, "Assembly Load Failed".1Yes

Extended Events
Assemblies (Database Engine)

Extended Events

Community Additions