Transaction Log

Technical Article

Help! My SQL Server Log File is too big!

  • Article

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.

2008-10-28

6,699 reads

Blogs

Advice I Like: Respect

By

“Don’t aim to have others like you; aim to have them respect you.” –...

Blue Sky Programming – The Optimism Trap

By

Many years ago, before I joined Oracle, I was working on a major modernisation...

Setting Up a Mac for Data Engineering and AI Work

By

If you work with data pipelines, SQL, notebooks, or machine learning models, a Mac...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

locking down agent for new user on our dev machine

By stan

hi , a new user wants to be able to add sql agent jobs...

SQL Server Enum Implementation: A Single-Row View Strategy for Avoiding Magic Values

By Ivica Borscak

Comments posted to this topic are about the item SQL Server Enum Implementation: A...

Visit the forum

Question of the Day

BIT_COUNT I

In SQL Server 2025, I have a table (dbo.UserPermission) that contains this data: 

UserID  UserPermissions
15
23
37
What is returned when I run this code: 
select bit_count(UserPermissions) as PermissionCount
from dbo.UserPermission
where UserID = 3;

See possible answers