SQL Server transaction log usage per session (4312230)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

SQL Server transaction log usage per session
Description

Is there a way for Foglight to identify the session which was responsible for the growth of a database's transaction log file?
Cause

SQL Server does not store the relation between session and file usage directly and hence it is unavailable.
Resolution
SQL Server does not store the relation between session and file usage directly and hence it is unavailable. The following could be used for identifying related problems:
- From SQL Performance Investigator (SQL PI) it is possible to see how much logical and physical reads a session consumed overtime; this will not show exactly which file, but can point to possible problem sessions.
- From SQL Performance Investigator (SQL PI), the "Command Types" dimension can be reviewed for "INSERT / UPDATE / DELETE" activities that would typically consume transaction log space; drilling down from that dimension can provide additional information on the related users, sessions and queries.
Additional information is available on the "Monitoring SQL Performance with SQL PI Configured" section of the Foglight for SQL Server User and Reference Guide.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title