Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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've written a small app to periodically query, sanitize, and insert a legacy database's data into SqlServer. There are about 3M records and, if I make the polling widow pretty small, I can imagine the transaction log getting pretty big. How can I minimize its growth during these "copy" operations?

share|improve this question
up vote 8 down vote accepted

How are you inserting data?

Bulk-logged recovery model can be your friend here.

share|improve this answer

Massimo is right. Specifically, you want to read this article - it lists the prerequisites for bulk logging to take place:

share|improve this answer

Depends on the backup mode of the target database.

If simple, the transaction log space should be freed and reused as transactions are committed, limiting space used.

Otherwise you will need to perform transaction log back ups.

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.