From: reb01501@NOSPAMyahoo.com   
      
   With Autogrow on, the database is already as big as it needs to be   
   (depending on how long it's been since the last restart). The size of your   
   application database is not really relevant unless you're doing thins like   
   sorting in tempdb. Even still, autogrow has already made tempdb as big as it   
   needs to be. Why are you blaming tempdb for your sluggish performance? Are   
   you noticing that many waits while tempdb is resized?   
      
   That said, however, as Erland put it, 200 Mb is nothing. Go for it. Then   
   monitor it for a while to see if it remains at 200 Mb.   
      
   m wrote:   
   > We have bad performanse on that SQL server,   
   > I noticed that tempdb is smaller than it should be (producer of   
   > software we use on that sql server advice to have inital min 100MB of   
   > tempdb)   
   > Now initial size of tempdb is 8MB with 10% of autogrowth and size is   
   > 90MB and application database is about 4GB.   
   >   
   > I'm planing to put inital 200MB with autogrowth 25%   
   > What do you think?   
   >   
   >   
   > "Bob Barrows"  wrote in message   
   > news:jct0hl$dis$1@dont-email.me...   
   >> m wrote:   
   >>> Hello,   
   >>>   
   >>> I need to increase tempdb database on SQL Server 2008 R2.   
   >>>   
   >>> Can I do it in business hours?   
   >>> Is there any negative inpact on the system?   
   >>>   
   >> Why? Had you trned autogrow off? I believe you can turn it back on   
   >> without restarting.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)