Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

allocation page contention in tempDB? Expand / Collapse
Author
Message
Posted Saturday, January 28, 2012 4:48 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 8:55 PM
Points: 1,076, Visits: 3,054
Hi,

In my production database have 1:1 data & log file..as per this script no result is dispaly, so no need to add more data file in tempdb database. Is it correct? could suggestion pls.

Select session_id,
wait_type,
wait_duration_ms,
blocking_session_id,
resource_description,
ResourceType = Case
When Cast(Right(resource_description, Len(resource_description)
- Charindex(':', resource_description, 3)) As Int) - 1 % 8088 = 0 Then 'Is PFS Page'
When Cast(Right(resource_description, Len(resource_description)
- Charindex(':', resource_description, 3)) As Int) - 2 % 511232 = 0 Then 'Is GAM Page'
When Cast(Right(resource_description, Len(resource_description)
- Charindex(':', resource_description, 3)) As Int) - 3 % 511232 = 0 Then 'Is SGAM Page'
Else 'Is Not PFS, GAM, or SGAM page'
End
From sys.dm_os_waiting_tasks
Where wait_type Like 'PAGE%LATCH_%'
And resource_description Like '2:%'

Thanks
ananda
Post #1243200
Posted Saturday, January 28, 2012 4:58 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Today @ 5:25 AM
Points: 9,928, Visits: 11,204
Opinions vary on this, but my own view is that it is only worth creating extra equally-sized tempdb files if you are experiencing allocation contention. Some people prefer to add the extra files to avoid the problem before it materializes, but there can be unwanted side-effects, including slowing down sorts and hashing operations that use tempdb. Overall, my vote would be for you to leave things as they are, but to continue to monitor for allocation contention, just in case.



Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #1243201
Posted Saturday, January 28, 2012 5:08 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 8:55 PM
Points: 1,076, Visits: 3,054
Thanks SQL Kiwi for your reply..

SQL Kiwi (1/28/2012)
Overall, my vote would be for you to leave things as they are, but to continue to monitor for allocation contention, just in case.


ok, I should continue to monitor for allocation contention in tempdb.

In cause of if very big sorting operation or sql jobs are running long time for particular time period that time tempdb will be allocate some contention during this activity completion after that what will happend? contention should be their in database or automatically will relase once completed these type of Jobs.

Thanks
ananda
Post #1243204
Posted Saturday, January 28, 2012 5:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:13 AM
Points: 40,609, Visits: 37,070
SQL Kiwi (1/28/2012)
Opinions vary on this, but my own view is that it is only worth creating extra equally-sized tempdb files if you are experiencing allocation contention.


My preference too, although if I have a case where I know that no one will bother to monitor, I may be proactive and create a 2nd file even without seeing contention.

That said, that script is wrong. It's looking at page numbers that are not PFS, GAM, SGAM pages (other than the 1st set in the file).

PFS - first PFS page is page 1, after that where PageNo % 8088 = 0 (no -1 required)
GAM - first GAM is at page 2, after that where PageID % 511232 = 0 (no -2 required)
SGAM - first SGAM is at page 3, after that where (PageID-1)%511232=0 (not -3 )

Easy to prove, by the formula in the script posted, page 511234 (511234 - 2 = 511232. 511232 % 511232 = 0) should be a GAM page, ie page type 8. Go and look at that in a DB big enough, and I get this:

Page @0x0000000080BA0000

m_pageId = (0:0) m_headerVersion = 0 m_type = 0
m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x0
m_objId (AllocUnitId.idObj) = 0 m_indexId (AllocUnitId.idInd) = 0 Metadata: AllocUnitId = 0
Metadata: PartitionId = 0 Metadata: IndexId = -1 Metadata: ObjectId = 0
m_prevPage = (0:0) m_nextPage = (0:0) pminlen = 0
m_slotCnt = 0 m_freeCnt = 0 m_freeData = 0
m_reservedCnt = 0 m_lsn = (0:0:0) m_xactReserved = 0
m_xdesId = (0:0) m_ghostRecCnt = 0 m_tornBits = 0


That's just an unallocated page. Check my formula though (PageID % 511232), it says that 511232 is a GAM.

Sure enough...
Page @0x0000000080B9C000

m_pageId = (1:511232) m_headerVersion = 1 m_type = 8
m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x200
m_objId (AllocUnitId.idObj) = 99 m_indexId (AllocUnitId.idInd) = 0 Metadata: AllocUnitId = 6488064
Metadata: PartitionId = 0 Metadata: IndexId = 0 Metadata: ObjectId = 99
m_prevPage = (0:0) m_nextPage = (0:0) pminlen = 90
m_slotCnt = 2 m_freeCnt = 6 m_freeData = 8182
m_reservedCnt = 0 m_lsn = (6664:3406110:62) m_xactReserved = 0
m_xdesId = (0:0) m_ghostRecCnt = 0 m_tornBits = 533630942

Trivial to show similarly that 511233 is an SGAM.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1243205
Posted Saturday, January 28, 2012 5:32 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:13 AM
Points: 40,609, Visits: 37,070
ananda.murugesan (1/28/2012)
In cause of if very big sorting operation or sql jobs are running long time for particular time period that time tempdb will be allocate some contention during this activity


Probably not. Growth maybe, but not contention. Contention comes from lots and lots and lots of small operations, not a single large one.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1243206
Posted Saturday, January 28, 2012 5:36 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 8:55 PM
Points: 1,076, Visits: 3,054
Hi thanks Gail for your clarification, Could you please post the correct script?

thanks
ananda
Post #1243208
Posted Saturday, January 28, 2012 5:44 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:13 AM
Points: 40,609, Visits: 37,070
I gave you the correct formulas, you should be able to correct the script given those.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1243209
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse