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 ««12

Index and Page Split Expand / Collapse
Author
Message
Posted Sunday, August 3, 2014 10:06 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: Yesterday @ 4:08 PM
Points: 40,177, Visits: 36,580
WhiteLotus (8/3/2014)
GilaMonster (8/3/2014)
murnilim9 (7/30/2014)
Moreover , I noticed the PAGE SPLIT/Sec is still high ..around 90 . How do i know which table that cause that page split ?


That counter is misleading. It is not the number of mid-index page splits (which are the ones which cause fragmentation)


Hi..
Thx for your response ...I wonder what do you mean by mid-index page splits ?



Page splits which occur in the middle (anywhere other than the ends) of an index, resulting in fragmentation.



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 #1599060
Posted Sunday, August 3, 2014 7:21 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 11:41 PM
Points: 119, Visits: 271
Jeff Moden (8/3/2014)
WhiteLotus (8/3/2014)
Jeff Moden (8/1/2014)
You could disable them which drops all of the data from the index but keeps the meta data and see if peformance suffers. Of course, you need to do a test on whatever is using the indexes before you do that. If performance does suffer, rebuild the index and it will reform, data and all.

Of course, there are the normal warnings about doing this on high usage or large tables during business hours and that such action could cause some substantial logfile growth like any index reorg (no matter the recovery model) or index rebuild (in the FULL recovery model) can cause.


Thanks for your response ..It is a good idea .. I could disable 1 index that has zero index seek but I highly hesitate to disable the others that has high number of index seek ...

I still don't know what to do with the indexes that have high number of index seek....


Apologies... I was relying on the flow of this thread to avoid having to include specific context...

Of course you wouldn't disable indexes with a large number of index seeks. You would only do such a thing on indexes that had little or no seeks compared to updates. Scans on indexes would definitely be a judgement call after some further investigation to see if the index could/should (not all should necessarily be) be modified to use seeks.

You would also avoid disabling UNIQUE indexes whether they have seeks or scans against them or not.


I have dropped the index but I still have the script to create the index .... and i will keep monitoring the performance of the query ....

Post #1599098
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse