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

Excellent article on securing msdb

By

Fabiano Amorim has written an excellent article at Simple Talk on securing msdb. Here's...

T-SQL Tuesday #201: Temp Tables

By

This month we have a new host, which I am grateful for. So many...

When Do You Reach For A #temp Table?

By

I needed to do some research because there is more to #temp tables than...

Read the latest Blogs

Forums

jdbc auth failing to sql from sap's cloud middleware CPI

By stan

hi , our business partner is asking s4 sap api's for receivable info and...

Searching for my own posts

By pietlinden

I have a really stupid question... Is there an easy way to search for...

How to Work with On-Premises AI Models to Generate T-SQL Code

By Daniel Calbimonte

Comments posted to this topic are about the item How to Work with On-Premises...

Visit the forum

Question of the Day

Escaping Strings

The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?

See possible answers