469,962 Members | 2,265 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,962 developers. It's quick & easy.

Re: tempdb size question

On Apr 3, 7:29*am, "Krisnamourt via SQLMonster.com" <u21487@uwe>

TempDB is the soul of SQL and everything you can do to gain performance, do

See this article from Kimberly and try to make this configuration. You'll see
the diference!


For example, SQL OLTP with 4 processors, I create five files, 4 with the same
size without autogrow and the last one with the same size, but with autogrow
true, because we need to garantee space for any necessary task, but often we
don't need and we manager well this.


aj wrote:
SQL Server 2005 SP2
I know that, for OLTP, the rule of thumb for LOGS is around 25% of
database size.
What is the rule of thumb for TEMP size? *I know that its a good idea
(for TEMP) to have .25 to 1 data files per CPU, but how big should
TEMP be in total? *Whats the rule of thumb there? *I would assume its
some multiple of the total size of all databases in the instance?

Message posted via SQLMonster.comhttp://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-general/200804/1

-For a small db server that does about 10-20 GB of logging per day, I
would recommend having a size that does not go through AUTO_GROW. i.e
ensure that the size of tempdb is big enough that it will hold the
whole days work.

- for larger dbs, you need to come up with a cycle time that is
sufficient for your applications. i.e a 30 minute to 3 hour growth
between tempdb's log file ie zero'ed.
Jun 27 '08 #1
0 1586

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by New DB Admin | last post: by
3 posts views Thread by Deaconess | last post: by
8 posts views Thread by arijitchatterjee123 | last post: by
3 posts views Thread by Kurt | last post: by
2 posts views Thread by Thomas R. Hummel | last post: by
1 post views Thread by rainxy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.