Administration

External Article

Find SQL Server databases where log file is too large

  • Article

I support thousands of databases and I'm running across situations where I have a database that has a data file of a couple hundred megabytes and the associated log file is gigabytes in size! I understand this is because I may not have my transaction log backups scheduled properly. What I'm interested in is an easy way to identify these situations where the SQL log file is too large, so I can go in and further analyze these problem databases without needing to look at each database.

2011-05-09

5,073 reads

Blogs

Finding Balance: Things Will Come Up

By

I have a presentation on finding balance in your career that got quite a...

Who Are You Doing It For?

By

But as I've matured over the years, I came to realize that I needed...

Presenting Twice in May 2026

By

I will be presenting my latest session, Documenting Your Work for Worry-Free Vacations, in-person...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

Migrate SSRS Reports to PowerBI Report Server in SQL Server 2025

By Deepam Ghosh

Comments posted to this topic are about the item Migrate SSRS Reports to PowerBI...

Identities and Sequences III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identities and Sequences III

Visit the forum

Question of the Day

Identities and Sequences III

When thinking of the Identity property for auto incrementing columns and sequences for the same action, which can be used with the BIGINT data type?

See possible answers