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

AI: Blog a Day – Day 8: RAG – Retrieval Augmented Generation

By

RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...

AI: Blog a Day – Day 7: Vector and Vector Databases

By

Continuing from Day 6 we learned Embeddings, Semantic Search and Checks, on Day 7...

AI: Blog a Day – Day 6: Embeddings – How AI Understands

By

Continuing from Day 5 where we covered notebooks, HuggingFace and fine tuning AI now...

Read the latest Blogs

Forums

Not Just an Upgrade

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Not Just an Upgrade

Restoring On Top I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top I

Designing Delta Tables with Liquid Clustering: Real-World Patterns for Data Engineers

By mehul.bhuva@gmail.com

Comments posted to this topic are about the item Designing Delta Tables with Liquid...

Visit the forum

Question of the Day

Restoring On Top I

I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens? 

USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO

USE DNRTest
GO
CREATE TABLE MyTest(myid INT)
GO
USE master
RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE

See possible answers