dbTalk Databases Forums  

DTS huge log file

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS huge log file in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Joca
 
Posts: n/a

Default DTS huge log file - 07-09-2003 , 05:02 PM






Hi,

I have 5 DTSsses that are executed by a Main DTS. All packages insert
lots of data into our DB. I've noticed that our Server's transaction
log reached its limit of 100 GB. We cleaned the log file and now we
are back in business. What is the best practice when inserting lots of
data into the db? What to do about the Transaction Log file fenomenal
growth ratio??? How to commit these transactions before executing the
next DTS?

I've read about doing batch inserts of 1000 rows, and checkpoint...
How to do checkpoint?

Thanks in advance!

Reply With Quote
  #2  
Old   
Ray Higdon
 
Posts: n/a

Default DTS huge log file - 07-09-2003 , 05:22 PM






Couple things:

You might want to drop any existing indexes before you
insert the data, if you are deleting an entire table, use
truncate instead of delete (minimal-logged), think about
using BCP, bulk insert or select into (if possible, they
are minimally logged as well)

You also might want to run in batches and truncate your
log in between batches (again, depends on when and on what
your inserts occur on)

HTH

Ray Higdon MCSE, MCDBA, CCNA
Quote:
-----Original Message-----
Hi,

I have 5 DTSsses that are executed by a Main DTS. All
packages insert
lots of data into our DB. I've noticed that our Server's
transaction
log reached its limit of 100 GB. We cleaned the log file
and now we
are back in business. What is the best practice when
inserting lots of
data into the db? What to do about the Transaction Log
file fenomenal
growth ratio??? How to commit these transactions before
executing the
next DTS?

I've read about doing batch inserts of 1000 rows, and
checkpoint...
How to do checkpoint?

Thanks in advance!
.


Reply With Quote
  #3  
Old   
Joca
 
Posts: n/a

Default Re: DTS huge log file - 07-10-2003 , 07:09 AM



Thanks for the follow up,

Im gonna run it in batches, i cannot use Bulk Copy. How do I truncate
the log in between batches?

thanks in advance!


"Ray Higdon" <rayhigdon (AT) higdonconsulting (DOT) com> wrote

Quote:
Couple things:

You might want to drop any existing indexes before you
insert the data, if you are deleting an entire table, use
truncate instead of delete (minimal-logged), think about
using BCP, bulk insert or select into (if possible, they
are minimally logged as well)

You also might want to run in batches and truncate your
log in between batches (again, depends on when and on what
your inserts occur on)

HTH

Ray Higdon MCSE, MCDBA, CCNA
-----Original Message-----
Hi,

I have 5 DTSsses that are executed by a Main DTS. All
packages insert
lots of data into our DB. I've noticed that our Server's
transaction
log reached its limit of 100 GB. We cleaned the log file
and now we
are back in business. What is the best practice when
inserting lots of
data into the db? What to do about the Transaction Log
file fenomenal
growth ratio??? How to commit these transactions before
executing the
next DTS?

I've read about doing batch inserts of 1000 rows, and
checkpoint...
How to do checkpoint?

Thanks in advance!
.


Reply With Quote
  #4  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: DTS huge log file - 07-10-2003 , 07:31 AM



Are you using FULL recovery model? If so then you don't want to truncate
the log, you should issue a log backup. If your not intending to do log
backups then set the recovery mode to Simple and you shouldn't have to worry
about it. I suspect that you have it in Full and are not doing regular log
backups and that is why the log has grown so large.

--

Andrew J. Kelly
SQL Server MVP


"Joca" <jjone99 (AT) hotmail (DOT) com> wrote

Quote:
Thanks for the follow up,

Im gonna run it in batches, i cannot use Bulk Copy. How do I truncate
the log in between batches?

thanks in advance!


"Ray Higdon" <rayhigdon (AT) higdonconsulting (DOT) com> wrote

Couple things:

You might want to drop any existing indexes before you
insert the data, if you are deleting an entire table, use
truncate instead of delete (minimal-logged), think about
using BCP, bulk insert or select into (if possible, they
are minimally logged as well)

You also might want to run in batches and truncate your
log in between batches (again, depends on when and on what
your inserts occur on)

HTH

Ray Higdon MCSE, MCDBA, CCNA
-----Original Message-----
Hi,

I have 5 DTSsses that are executed by a Main DTS. All
packages insert
lots of data into our DB. I've noticed that our Server's
transaction
log reached its limit of 100 GB. We cleaned the log file
and now we
are back in business. What is the best practice when
inserting lots of
data into the db? What to do about the Transaction Log
file fenomenal
growth ratio??? How to commit these transactions before
executing the
next DTS?

I've read about doing batch inserts of 1000 rows, and
checkpoint...
How to do checkpoint?

Thanks in advance!
.




Reply With Quote
  #5  
Old   
Joca
 
Posts: n/a

Default Re: DTS huge log file - 07-10-2003 , 01:05 PM



Yes, at first the recovery model was set to Bulk-logged. We've set it
to simple now. We don't really need to log any transaction while the
DTSs run.

Did you say that I don't need to type CHECKPOINT after I execute each
DTS? Also, not sure if this has happened to anyone else, is it
possible that if the transaction log is full then stored procedures w/
cursors and temp tables will not run correctly??

Thank you in advance for all the shared knowledge!

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.