Log File Auto Shrink Event Class
The Log File Auto Shrink event class indicates that the log file shrank automatically. This event is not triggered if the log file shrinks because of an explicit ALTER DATABASE statement.
Include the Log File Auto Shrink event class in traces that monitor the shrinking of the log file. When thisevent class is included in a trace the amount of overhead incurred will be low unless the file frequently shrinks.
Data column name
Name 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.
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 client process ID.
ID 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.
Name of the database in which the user statement is running.
Length of time (in milliseconds) necessary to extend the file.
Time that the log file Auto Shrink ended.
Type of event = 95.
Sequence of the CursorClose event class in the batch.
Logical name of the file being extended.
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.
Number of 8-kilobyte (KB) pages by which the file increased.
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 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.
Windows domain to which the user belongs.
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.
Time at which the event started, if available.