Why is the tempdb much more faster ?

Hi,

Why is the tempdb much more faster than the other dbs (SQL2000 & SQL2005)?

I've created some testdbs using the same physical locations for the ldf & mdf file like for the tempdb. And I've also set up the same db-settings.

on sql2000 the tempdb is about 50% to 70% faster and on sql2005 about 1000%!!!

ok...it's nice to have such a fast tempdb...but why???

here's the testscript:
CREATE TABLE Numbers(ID INT NOT NULL PRIMARY KEY)
GO
SET NOCOUNT ON
DECLARE @Index INT
SET @Index = 1
WHILE @Index <= 8000
BEGIN
INSERT Numbers (ID) VALUES (@Index)
SET @Index = @Index + 1
END
GO
DROP TABLE Numbers
GO

Is this a usual behaviour?

Regards,
Dominic

Thanks for your answer...Ok...I'll try to use the tempdb so much as I can...<img src='/community/emoticons/emotion-1.gif' alt='' /><br /><br />Hmm...so there is no chance to get running the usual db's so fast as well....? It looks like...:-(<br /><br /><br /><blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by satya</i><br /><br />SQL Server 2005 makes greater use of tempdb than SQL Server 2000 did, so its better in locating tempdb on its own high-performance drive system.<br /><br />New features of tempdb scalability with SQL 2005 are:<br />- Caching of IAM and first data page for temp table and table variables. <br />- Improved allocation page latching protocol so that we use UP latch less frequently. <br />- Reduced logging overhead for tempdb so that we consume less IO bandwidth in tempdb log file. <br />- More efficient allocation algorithm for mixed pages in tempdb. <br /><br />I would recommend the following if you see lot of contention in TEMPDB:<br /><br />- Avoid auto grow<br />- Allocate space for tempdb files<br />- Make sure temp tables are cached <br /><br />Moreover the objects in tempdb are cleared once the session is closed or the connection is closed, so you do not have any contention there to refresh the optimization.<br /><br /><br /><hr noshade size="1"><b>Satya SKJ</b><br />Microsoft SQL Server MVP<br />Contributing Editor & Forums Moderator<br /<a target="_blank" href=http://www.SQL-Server-Performance.Com>http://www.SQL-Server-Performance.Com</a><br /><center><font color="teal"><font size="1">This posting is provided “AS IS” with no rights for the sake of <i>knowledge sharing.</i></font id="size1"></font id="teal"></center><br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote">

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">Ok...I'll try to use the tempdb so much as I can...<img src='/community/emoticons/emotion-1.gif' alt='' /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote">Well, there is a good reason why it is beneficial that tempdb has some degree of priority on the server. If you start using tempdb by yourself, you'll lose the benefits.<br /><br />You should be aware that tempdb is a SYSTEM database, which you should leave to SQL Server to work with.