Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to look for the process/processes that is causing the transaction log to grow out of control. I have tried setting the DB to Bulk-Logged and it seems to still be growing. When set to Simple when the process/processes finish it clears. Profiler shows statements that start with "Insert Bulk xxxx" which I been reading about, but one thing I cannot determine is if "Insert Bulk" logs or not with the BULK-Logged setting. Can anyone give me your thoughts on the "Insert Bulk" command

share|improve this question

Even in the bulk-logged recovery model, even with operations that are minimally logged, you still need to take transaction log backups regularly - SQL Server still writes the allocation changes to the transaction log. How does the operation compare to when the database is in full recovery - in terms of speed, and transaction log backup sizes?

I'm sure you've read the pre-reqs:

share|improve this answer
While I do understand what is logged in BL I am trying to find out if insert bulk logs everything. I am looking for something that takes an empty 21GB log file and increases it to 60-70GB 99% used before it releases and goes back to 0% used. – CWL Apr 1 '11 at 17:24

You may want to look at the post.

If doesn't help then add more details and share the code snippets.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.