Improve tempdb Performance (SQL Server BPA)

this is bpa recommendation :
 If the previous steps do not significantly reduce the allocation  contention and the contention is on SGAM pages, implement trace flag  -T1118. Under this trace flag, SQL Server allocates full extents to each  database object, thereby eliminating the contention on SGAM pages. Note
 that this trace flag affects every database on the instance of SQL

 For information about how to determine whether the allocation contention
 is on SGAM pages, see "Monitoring contention caused by DML operations" in
 Working with tempdb in SQL Server 2005. To address immediate problems,
 use trace flag -T1118; however, we recommend that you consider
 implementing longer-term, scalable, solutions. For example, you might have
 to modify queries to limit the use of table variables, temp tables, or

how can we do this , or there is better ways to handle this. if so please though your ideas.

thanks '
Who is Participating?
Eugene ZConnect With a Mentor Commented:
Troubleshooting Performance Problems in SQL Server 2005
Tempdb Configuration Best Practices in SQL Server
Optimizing tempdb Performance 
rob_farleyConnect With a Mentor Commented:
At the moment my favourite way of optimising tempdb is to put it on a Solid State Disk. With much faster reads & writes, it helps a lot.

And if the drive fails, remember that tempdb isn't used as a permanent data store anyway. You just restart the service and tempdb gets wiped anyway (but heck - get two in RAID1 and you're basically as safe as you need).

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.