going on. Even if you could disable it (I'm not sure if you can), it's
probably not a good idea.
What I've done for such large jobs, is bust 'em up into smaller chunks.
Set up some sort of looping that runs your process in chunks of 10,000
or 25,000 records, or something like that. Then your transaction logs
will stay smaller (10,000 record-size instead of 1 million). And if
it's a nightly process, you probably won't mind the (slightly) longer
execution time. (I've had some cases were it was actually faster this
way, anyway!)
-----Original Message-----
From: Jerry Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, October 04, 2004 09:27
To: SQL
Subject: SQL Server DTS package question
I have a DTS package that populates a huge (to me) table from another
db. (1 million records)
Is there any way to turn off transaction logging for this table copy
without turning it off for the database as a whole?
The transaction log is growing uncontrollably large from this copy.(1 GB
a night)
Jerry Johnson
________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
