From: Dave on
One more thing: Keep your batches small (< 5000) otherwise your
update will take out a table lock. Play with your batchsize and
"paglock" hint to get the biggest batch that doesn't lock your table.

From: Enorme Vigenti on
imani_technology_spam(a) ha scritto:
> We have a table that contains billions of rows. When we try to UPDATE
> that table, we overload the transaction log. What are some ways to
> avoid this? Is there a way to "turn off" the transaction log
> temporarily?
my tips:
Split the big table into multiple "Patition Tables" (enterprise version