troubleshooting Question

Cannon shrink log file because of minimum log space required.

Avatar of vbchewie
vbchewieFlag for United States of America asked on
Microsoft SQL Server
7 Comments3 Solutions7005 ViewsLast Modified:
My transaction log for an 18GB database is usually around 2 to 4GB.  Last week it blew up to 21GB I think because of a reindexing management plan.  I have tried everything I can think of to get this back down to it normal size.  I have switched the database to Simple, shrunk the log, and switched back to full.  This database might have had a replication on it at some point but I know it shouldn't any more.  And I can't find anything under Local Publication or Local Subscriptions referring to this database.  

I perform transaction log backups every 30 min.  But it still says under the disk usage that all of the transaction log space is being used.  

How do I get this transaction log back down to its normal size?
Join our community to see this answer!
Unlock 3 Answers and 7 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 3 Answers and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros