Log File Auto Grow Event Class

Log File Auto Grow Event Class

 

Applies To: SQL Server 2016

The Log File Auto Grow event class indicates that the log file grew automatically. This event is not triggered if the log file is grown explicitly through ALTER DATABASE.

Include the Log File Auto Grow event class in traces that are monitoring the log file growth. When this event class is included in a trace the amount of overhead incurred will be low unless the log file is growing automatically frequently.

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 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
DurationbigintLength of time (in milliseconds) necessary to extend the file.13Yes
EndTimedatetimeTime that the log file auto grow ended.18Yes
EventClassintType of event = 93.27No
EventSequenceintSequence of CursorClose event class in batch.51No
FilenamenvarcharLogical name of the file being extended.36Yes
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
IntegerDataIntNumber of 8-kilobyte (KB) pages by which the file increased.25Yes
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 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.7Yes
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, if available.14Yes

Extended Events
sp_trace_setevent (Transact-SQL)
ALTER DATABASE (Transact-SQL)

Community Additions

ADD
Show:
© 2016 Microsoft