|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 5:48 PM
Points: 7,088,
Visits: 7,143
|
|
Thanks for teh question. It made me look in BoL, which some say is cheating (and I say is learning).
Tom Que conclure à la fin de tous mes longs propos? C'est que les préjugés sont la raison des sots. (Voltaire, 1756)
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:44 PM
Points: 1,786,
Visits: 3,323
|
|
| I had to do the same (look i BOL), but I don't consider that cheating. "Cheating" in my opinion is when you copy/paste/run the T-SQL and post the answer without utilizing a single neuron in the central nervous system.
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Yesterday @ 7:18 PM
Points: 10,989,
Visits: 10,532
|
|
SanDroid (12/14/2010)
Nils Gustav Stråbø (12/14/2010)
vk-kirov (12/14/2010) The bad news is that, according to BOL, "this view is applicable only to the tempdb database".I would not expect much change in SGAM pages in a normal database. Table creation rates should be low compared to tempdb, so frequent changes in SGAM page allocation is unusual. I believe this is more important to monitor when you are using Mirroing or Publishing a VLDB. Also it may be usefull you execute large querries (5K+ rows) that use TEMP tables or Table Parameters that have to create objects to store data in TEMPdB. No, Nils is quite correct.
I have no idea why you think mirroring, or publishing a large database would be a prime factor in tempdb SGAM contention. Where does your magic figure of 5K+ rows come from, or are you just guessing?
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|