May 21, 2009 at 7:08 am
Hi All,
I have a DTS package with a task that will load data from a mdb file and insert them into a table in Sql Server 2000. This package usually runs each 10 minutes from 6am to 10h30pm, every day.
During this time, I can see that my log file is increasing a lot and my question is if could I set up this task to not generate any kind of log.
What I am doing now is truncating the log file at the end of the day.
Thanks for your help.
Alex
May 21, 2009 at 10:19 am
You can't prevent SQL Server from writing to the transaction log. It's an integral part of the database engine. Since the package runs so often, you should consider running frequent log backups rather than truncating the log manually. I'm assuming the database is using the full recovery model.
Greg
May 21, 2009 at 10:28 am
Hi Greg,
Yes, the database is configured this way (full recovery) and twice a day, I'm performing a backup log.
Thanks for your explanation.
May 21, 2009 at 12:44 pm
Twice a day won't do much about keeping the logs manageable, but it really depends on how much update activity there is. I'd start with hourly backups and adjust from there.
Greg
May 21, 2009 at 2:58 pm
And do not truncate the log anymore. By doing that, you are breaking the log chain and eliminating the ability to perform point in time recovery. You have to perform a full backup before you can perform the next transaction log backup.
Please review the article I link to in my signature on how to manage the transaction logs. It will help you understand why the log is growing and how you really should be managing it.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply