I had a similar issue in our production environment where our transaction log was growing to unacceptable sizes after bulk data loads. In my case, the transaction log was not needed so I would manually truncate it after the inserts to get it back down to an acceptable size. I added this query at the end of my stored procedure to perform this:

EXEC sp_dboption 'db_name', 'trunc. log on chkpt.', 'TRUE'

USE db_name

CHECKPOINT

GO

DBCC SHRINKDATABASE (db_name, 10)