InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 17:38:42 GMT20http://www.sqlservercentral.com/Forums/Topic1039137-1357-1.aspxPoint taken, Brad. You are right that it is not needed to eat the entire egg in order to know it's spoiled. :hehe:On the other hand, in my organization today we barely have any tempdb less than 4Gb, and also, I really like to see my data through. Fri, 17 Jun 2011 13:34:49 GMTfeodor.georgievhttp://www.sqlservercentral.com/Forums/Topic1039137-1357-1.aspxFeodor, I am aware of this issue of the script, but it not really that important for two reasons. First, most tempdb databases are smaller than 4 GB. And two, even if they are larger than 4 GB, realizing that contention is happening in the initial allocation pages is enough information to know that you have a problem. It is kind of like taking the pulse of a person. While knowing the pulse doesn't give you the entire picture of somebody's health, it still is enough information to know if there is a potential problem or not.Fri, 17 Jun 2011 10:01:44 GMTbradmcgehee@hotmail.comhttp://www.sqlservercentral.com/Forums/Topic1039137-1357-1.aspxBrad, I would like to suggest a small correction to your script. Since the GAM and SGAM pages are repeated every 64000 extents (~4Gb), this means that you will have to introduce some logic in your script to check for this, especially in a high volume production systems, where the tempdb files are way beyond 4Gb. For example, you can use a formula similar to: for GAM pages: (the page ID is 2) % 511232for SGAM pages: (the page ID is 3) % 511232Otherwise your script will be inaccurate. Regards,Feodor GeorgievFri, 17 Jun 2011 03:34:15 GMTfeodor.georgievhttp://www.sqlservercentral.com/Forums/Topic1039137-1357-1.aspxComments posted to this topic are about the item [B]<A HREF="/scripts/tempdb/72008/">Identify Allocation Contention in TEMPDB</A>[/B]Fri, 24 Dec 2010 09:46:00 GMTbradmcgehee@hotmail.com