Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

133Gb LDF file!!!

I have been running out of disk space and tracked it down to my database EOC_Log.LDF file exceeding 130Gb - yes Gigabyte's.

I have attempted to shrink the file but it continues to stay around this size. I then stopped all Solarwinds services on this server and re-attempted to shrink - same thing.

This is the only database using SQL Server 2005.

Has anyone else seen this? How can I shrink this?

Find more posts tagged with

Accepted answers

All comments

Yann

Hi,

Could you check that your Recovery Model is set to simple for the EOC database?

http://technet.microsoft.com/en-us/library/ms189272(SQL.90).aspx

The SQL Server database transaction log file is maintained for recovery purposes, but it grows rapidly if you are not using the Simple Recovery model.

For more information about when the Log file is truncated: http://technet.microsoft.com/en-us/library/ms189085.aspx

How can I shrink this?

If you backup the database (try to save it across the network if local disks are full), it should move the checkpoint in the Transaction log file which will let you then shrink it to remove useless recordings.

To Backup the DB: http://msdn.microsoft.com/en-us/library/ms187510(SQL.90).aspx

To Shrink the DB: http://msdn.microsoft.com/en-us/library/ms189035(SQL.90).aspx

HTH,

Yann

FormerMember

Thanks Yann for the quick reply.

I just checked and it was set for Full. I since have changed it to Simple and shrank the log file which worked.

Was this documented somewhere and I missed it?

Thanks again!

Yann

Was this documented somewhere and I missed it?

This must be in the SQL Server 2005 documentation.

I am reading the following book which gives good details about how SQL Server 2005 works:

http://www.informit.com/store/product.aspx?isbn=0672328240

Database implementation is not covered in our documentation as this is a third party product.

derhally

This was an issue in version 1.0 of EOC and it looks like it didn't make it into our service packs.

This has been definately fixed in the next release and the logging is set to SIMPLE.