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

Walking Through a Planned Failover: SQL Server Availability Groups on Kubernetes

By

When building the sql-on-k8s-operator, I wanted to make sure it could handle both planned...

Reading SQL Server File Headers with DBCC FILEHEADER

By

I’ve been doing a deep dive into SQL Server on-disk structures lately, and one...

T-SQL Tuesday #197 – An impactful session or two from a conference – RECAP

By

Thanks to everyone who joined the blog party this month. I noticed three themes...

Read the latest Blogs

Forums

What's new in R 4.6

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What's new in R 4.6

Interesting Changes in R

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Interesting Changes in R, which...

PostgreSQL String Functions Part 1

By Shivayan Mukherjee

Comments posted to this topic are about the item PostgreSQL String Functions Part 1

Visit the forum

Question of the Day

Identities and Sequences V

When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?

See possible answers