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

The Mystery of the Locked-Up Database -Scooby Dooing Episode 6

By

No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...

Announcements from the Microsoft Fabric Community Conference

By

A bunch of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...

The Challenge of Implicit Transactions: #SQLNewBlogger

By

I saw an article recently about implicit transactions and coincidentally, I had a friend...

Read the latest Blogs

Forums

Compatibility levels on database changing them and impacts.

By jonluder

We’re running SQL Server 2019 with database compatibility level 150, and after recent tuning...

Changing the Recovery Time

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Recovery Time

Getting More Time from AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting More Time from AI

Visit the forum

Question of the Day

Changing the Recovery Time

I want to change the recovery time for a database running on SQL Server 2022. What are my options for setting the value in my ALTER DATABASE statement. If I run this code, what can I use in place of the xxx to define what 12 means?

ALTER DATABASE Finance 
 SET TARGET_RECOVERY_TIME = 12 xxx;

See possible answers