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

The 2026 Redgate Summit in New York City

By

We’re coming back to New York, which is exciting for me. I love NYC....

Monitoring Fabric Mirroring for SQL 2025

By

I previously wrote about how the underlying technology for Fabric mirroring changed with SQL...

Monday Monitor Tips: Intelligent Alert Thresholds

By

At the recent Redgate Summit in Chicago, I demo’d (lightly) the ML based Alert...

Read the latest Blogs

Forums

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Doing the Little Things

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Doing the Little Things

Visit the forum

Question of the Day

Historical Data Tracking

If I want to track historical data values, which mechanism should I use?

See possible answers