Technical Article

Help! My SQL Server Log File is too big!

Over the years, I have assisted so many different clients whose transactional log file has become "too large" that I thought it would be helpful to write about it. The issue can be a system crippling problem, but can be easily avoided. Today I'll look at what causes your transaction logs to grow too large, and what you can do to curb the problem.

SQLServerCentral Editorial

Barriers to Entry, Database Weekly (Oct 27 2008)

Many people who spend time contributing to technical forums bemoan the increasing amount of time and energy they expend trying to help people who seem unwilling or unable to help themselves. At the same time, they say, the courtesy is deteriorating and the number of people willing to "stir things up" for the sake of it increases. Is there a solution to this?

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