By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,850 Members | 1,771 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,850 IT Pros & Developers. It's quick & easy.

How to avoid Tran Fail Log error with update statements

P: n/a
vj
I have an update statement which updates 100,00 records and most often
I end up in a tran fail log error , is there any option which would
enable me to commit the updates in batches.

Please let me know if there are any work arounds.

Thanks,
Vj.

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
What type of logging are you using? If it's circular; then you've filled
up all of the primary and secondary logs. A simple solution is to
increase the log size or the number of logs. If this is a production
system; circular logging has other (negative) recovery implications.

You could use a WHERE predicate to restrict your updates to a portion of
your rows. Multiple UPDATES can be coded with a COMMIT between them.
Phil Sherman

vj wrote:
I have an update statement which updates 100,00 records and most often
I end up in a tran fail log error , is there any option which would
enable me to commit the updates in batches.

Please let me know if there are any work arounds.

Thanks,
Vj.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.