bmsande
asked on
SQL Transaction Log started growing a couple days ago
SQL 2008 R2 single instance, hosting one database
This week I was performing an analysis of our server to make sure SQL is configured in an appropriate manner. Using this question to guide me.
Since I started my analysis, our transaction logs have grown from 700 MB to 90 GB. I wasn't making changes that I'm aware of. I ran the Best Practice Analyzer and a few select statements.
What could cause my transaction logs to grow? How do I get them back to a manageable size?
This week I was performing an analysis of our server to make sure SQL is configured in an appropriate manner. Using this question to guide me.
Since I started my analysis, our transaction logs have grown from 700 MB to 90 GB. I wasn't making changes that I'm aware of. I ran the Best Practice Analyzer and a few select statements.
What could cause my transaction logs to grow? How do I get them back to a manageable size?
strivoli
Transaction Logs grow as you use SQL. You can shrink running backups and shrink jobs.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This system has been alive for years. We've never seen our transaction logs grow beyond 2 gig.
Since Monday, (5 days ago), our transaction log is 90 gig and rising.
Something changed, that's what I need to figure out. Then I need to fix it.
Since Monday, (5 days ago), our transaction log is 90 gig and rising.
Something changed, that's what I need to figure out. Then I need to fix it.
ASKER
Good to know about BPA @Victor. Thanks. I'll research your suggestion as it sounds like the likely reason and best fix.
Since I started my analysis, our transaction logs have grown from 700 MB to 90 GB. I wasn't making changes that I'm aware of. I ran the Best Practice Analyzer and a few select statements.I think you already figured it out :)