Transaction Log Files - Too big? 2

[ITDudeinphoenix]

Hi:

We recently installed a MS-SQL box which we will use to lookup tax rates based on the location of the ship to customer. We have not gone 'live' with the new system but i have noticed the log files growing at an alarming rate - at present approx. a 2 - 1 ratio. My question is can i delete the log files after a successful backup without causing any database issues?

Thank you in advance.

 

[SQLBill]

For the log files to be growing there has to be transactions happening.

You have some options depending on what is really occuring.

If the database is static, not being used for anything - you need to find out what's causing the transactions.

If the database is really 'live', but not available to users - then you need to decide how valuable your data is. Can you afford to lose data? If so, consider switching your Recovery Mode to SIMPLE.

If the data is valuable and you need to be able to recover up to the minute, you need to backup the transaction logs regularly.

First things first...make sure you have a full backup of your database(s). Then backup your logs regularly. Backing them up will also shrink them (this does NOT happen immediately).

Search the FAQs for this forum and the SQL Server: Programming forum for more information on the transaction logs, backups, etc.

-SQLBill

Before you post check out: FAQ481-4875 and FAQ222-2244

 

[Mich]

Each time you back up your trans log it should truncate unless specified otherwise. You may look at backing up your trans log more often to truncate it more often. I've heard of people backing up their ldf every 15 minutes or so just to keep its size relatively small.

-If it ain't broke, break it and make it better.