John S
John S

Reputation: 8331

Determining what is causing massive log file growth on an inactive SQL 2005 DB

I have a SQL DB in a test environment that is the back end datasource for a test web site. There is no activity on the website (because it is in our test environment), but every couple of days the DB log files grow extremely large, causing issues with backups, etc.

This is a test environment so there is no activity that we don't have control over. Why are the logs growing at all? And why so large?

I am looking for some tips on how to track down what is causing this log growth on an inactive site/DB.

I have looked for open transactions using DBCC OPENTRAN with the result of no open trans.

Any other ideas?

Upvotes: 0

Views: 465

Answers (1)

ktharsis
ktharsis

Reputation: 3190

Do you have any jobs running on a timed basis such as backups or optimizations? Doing a full rebuild of indexes as part of the maintenance job can cause the log files to be larger than expected (among other things - that is one of the most common).

Places to look in SSMS for jobs:
Management - Maintenance Plans
Management - Legacy (if you were using older versions of SQL at some point)
SQL Server Agent - Jobs

Upvotes: 1

Related Questions