June 2, 2008 at 2:56 pm
You may well have stumbled on a bug here -
I will do some more searching on the web for similar info.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
June 2, 2008 at 3:05 pm
Marios Philippopoulos (6/2/2008)
You may well have stumbled on a bug here -I will do some more searching on the web for similar info.
I find it hard to believe that its a bug, considering how many people use the DMV
My money is on the permissions the web user has, but this does not make too much sense, but its a possibility.
I too am scouring like a maniac- searching for useful info amongst the repeats of index usage stats info is getting hard 🙂
June 2, 2008 at 4:02 pm
from the blog of Colin Leversuch-Roberts http://sqlblogcasts.com/blogs/grumpyolddba/:
What I’ve found in large production systems is that you cannot guarantee that data on every index is held in the dmvs at all times...
Also, this link is loaded with very useful info:
http://sqlblogcasts.com/blogs/grumpyolddba/archive/2008/02/18/analysing-indexes-summary.aspx
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
June 2, 2008 at 4:32 pm
Marios Philippopoulos (6/2/2008)
from the blog of Colin Leversuch-Roberts http://sqlblogcasts.com/blogs/grumpyolddba/:What I’ve found in large production systems is that you cannot guarantee that data on every index is held in the dmvs at all times...
Also, this link is loaded with very useful info:
http://sqlblogcasts.com/blogs/grumpyolddba/archive/2008/02/18/analysing-indexes-summary.aspx
Thank you very much. A quick scan through the documents does not really shed more light though, as my DB at 45GiG is smaller and has far fewer indexes than that article mentions, and yet my stats are really far off. Microsoft makes me cry 20 years on still :/
June 2, 2008 at 6:03 pm
Stress (6/2/2008)
Marios Philippopoulos (6/2/2008)
from the blog of Colin Leversuch-Roberts http://sqlblogcasts.com/blogs/grumpyolddba/:What I’ve found in large production systems is that you cannot guarantee that data on every index is held in the dmvs at all times...
Also, this link is loaded with very useful info:
http://sqlblogcasts.com/blogs/grumpyolddba/archive/2008/02/18/analysing-indexes-summary.aspx
Thank you very much. A quick scan through the documents does not really shed more light though, as my DB at 45GiG is smaller and has far fewer indexes than that article mentions, and yet my stats are really far off. Microsoft makes me cry 20 years on still :/
Most people - myself included - take DMV results as written on stone.
After Colin's blogs and your current problem, I'm not so sure any more...
Makes me want to test this out myself.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply