From: Dave on 2 Oct 2009 02:01 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 2 Oct 2009 03:48 imani_technology_spam(a)yahoo.com 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 only).
First
|
Prev
|
Pages: 1 2 3 Prev: I'm a New bie to SQL SERVER 2005 Next: how to convert int to datetime |