I'm looking for a little guidance understanding how the SQL Transaction Log file behaves during a DTS Package run. I've read up on the subject at the MSDN site but am experiencing some results that I don't understand. Background: I have a DTS package that basically reads in data from an MS Access DB into a SQL Server DB. It has many steps, some of which alter the Access DB prior to the import, and some of which deal with the data in the SQL Server. The data coming in from Access is fairly small, but the package moves larger amounts of data around within the SQL Server. Problem: One particular SQL Task errors off frequently. This task is attempting to copy about 2 million reacords from one table to another within the SQL Server: insert into TABLE1 select * from TABLE2 The error that is occurring is "The log file for database 'DB_NAME' is full. Back up the transaction log for the database to free up some log space. ". I have set every single step within the package (including those that deal with the MS Access DB) to commit after successful execution of the step. The DBA says the log file for this DB is already a huge percentage of the DB and shouldn't be increased. Here's the weird part. Even though this step fills up the log file when executing in the package, I can run it manually by right-clicking on the step and selecting Execute Step. It runs OK and doesn't receive the error. My conclusion is that the step isn't filling up the log file itself, but the entire package is. However, I assumed that the log would be cleared after each step since I have them all set to commit after execution. Any guidance as to why I may be seeing this problem would be greatly appreciated. I'm looking into changing the step to commit after a certain number of records, but I'm suspicious that this won't resolve the error since the step can run fine by itself. Is there some way to ensure that the log file is getting cleared during the execution of a DTS package?