SQL SERVER – Reducing Page Contention on TempDB
Posted
by pinaldave
on SQL Authority
See other posts from SQL Authority
or by pinaldave
Published on Wed, 26 Jan 2011 01:30:43 +0000
Indexed on
2011/01/28
23:30 UTC
Read the original article
Hit count: 567
Pinal Dave
|PostADay
|sql
|SQL Authority
|SQL Query
|SQL Scripts
|SQL Server
|SQL Tips and Tricks
|T SQL
|Technology
|SQL TempDB
|tempdb
I have recently received following email.
“We are using TraceFlag 1118 to reduce the tempDB contention on our servers (2000 and 2005). What is your opinion?
We have read lots of material, would you please answer me in single line.”
Wow, this was very interesting question. What intrigued me was the second last where I am asked to answer in a single line. There is something about this strong email, I feel like blogging it here.
I think I can talk over this subject forever – well, there is no clear answer. There are so many caveats about everything. Again, I must stay honest to the request about answering in single line. I also do not like to answer which is YES/NO. What should I do?
Let me ask this question to community today? What will you answer to this email?
Let me start this by answering it myself in one line and taking one side.
“I enable this trace flag in SQL Server 2000 without hot patch or service pack and not in later versions (2005+) onwards as code is improved”.
What do you do in this case? The best answer will feature in this blog with due credit.
Regarding further read and hint here is Microsoft KB which I think is very helpful.
In quick summary: (Read KB for accuracy)
When any page is allocated first 8 pages are allocated in mixed extended. This trace flag allocates uniform extended at the time, reducing contention. You can enable this trace flag at startup.
Reference: Pinal Dave (http://blog.SQLAuthority.com)
Filed under: Pinal Dave, PostADay, SQL, SQL Authority, SQL Query, SQL Scripts, SQL Server, SQL Tips and Tricks, T SQL, Technology Tagged: SQL TempDB, TempDB
© SQL Authority or respective owner