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

SQL Server is Slow, part 3 of 4

By

In parts 1 and 2 of this series, we’ve gathered info and done the...

AI Model Size, Parameters and Download

By

At SQL Saturday Boston 2025, I gave a presentation on local LLMs and there...

Expanding Your DBA Horizons: Installing PostgreSQL in a Home Lab

By

Are you diversifying your DBA skillset? My recent job search made one thing clear:...

Read the latest Blogs

Forums

caught off guard by some greek lettering in a warehouse feed

By stan

Hi we run 2019 standard.   Our warehouse's ssis based etl is klunky but so...

Unlocking High-Concurrency Inserts in SQL Server with OPTIMIZE_FOR_SEQUENTIAL_KEY

By Chandan Shukla

Comments posted to this topic are about the item Unlocking High-Concurrency Inserts in SQL...

Vector Datatype

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Vector Datatype

Visit the forum

Question of the Day

Vector Datatype

The new Vector datatype in SQL Server 2025 is a binary type that has a few parameters. What parameters are required?

See possible answers