Hi guys,

I dont know if im in the right group.  My scenario is like this.
Transaction logs are eating up my server's hard drive. Almost 60% of my
space is transaction log.  What are these? Can I simply delete it? Can I
compress this?  Can someone explain this log file.

Thank you in advance.



Allan M. Grafil

Allan M. Grafil wrote:
You need to backup the transaction log regularly or switch to simple
recovery model. For more information, see:
http://technet.microsoft.com/en-us/library/ms189275.aspx
http://support.microsoft.com/kb/873235

Too add Razvan's comment backup is the perfered manner; but I know some
people just simply truncate the logs and shink the or regular basis because
they don't need to the point-of-failure restores.

BACKUP LOG DBNAME WITH NO_LOG
DBCC SHRINKFILE file, targetsize

Thanks!
Show quoteHide quote

Allan M. Grafil (agra***@hotmail.com) writes:
First of all: never, I repeat NEVER delete your log file.

Next: decide, what level of recovery do you need? If your database goes
belly-up, are you content with restoring the most recent backup, or do
your business require up-to-the-point recovery?

In the first case, run ALTER DATBASE db SET RECOVERY SIMPLE and run
DBCC SHRINKFILE with a target size that is 20-25% of your data file.
Please check Books Online for the exact case. With simple recovery, the
transaction log is frequently truncated. You should still have some
size to permit for huge transactions. If you make it too small, it
will grow, but growing steals performance.

If you need up-to-the-point recocvery, you need backup the transaction
log regularly, probably at least as often as once an hour. If you don't
back up the log, it just keeps growing.

Generate SQL scripts in Management Studio
Utility to read transaction logs
CPU-bound or I/O bound?
Re: SQL Profiler 2005
can someone have idea on this perfmon result