3398b145   
   From: thomas@seidel-gammelby.de   
      
   Possibly it is worth to try a bigger machine? SQL 2008 on Win2008Server with   
   lots   
   of RAM might solve a performance problem like yours, its worth a try, isn't it?   
      
   TAS   
      
      
   imani_technology_spam@yahoo.com wrote:   
   > 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?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)