Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
 Posted - 2010-04-01 : 01:47:16
|
 I know it is an art not a science and that there are lots of factors to consider but based on these stats would you be inclined to delete the three indexes with only about 1000 seeks?Thanks. |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-01 : 03:46:34
|
| All created by Index Tuning wizard? If so they were probably created without actually considering if any were actually useful! |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-04-01 : 06:24:08
|
| No way to tell from that. Post the index definitions - key columns and include columns.--Gail ShawSQL Server MVP |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-04-16 : 03:36:14
|
quote:
Originally posted by ferrethouse
Obviously the lower the read/write ratio the more likely that the index should be deleted.
Not necessarily. You have to be sure with this kind of thing that you've got data from the entire business cycle. If stuff is run at month end and never any other time, then you must have data from month end. If stuff is run at year end and never any other time, then you must have data from year end.Imagine if one of those that shows low usage is critical for a month end report?Can you post definitions? From the looks of things, one of those indexes is a duplicate and can be safely dropped without impact, but would like to see index definitions to be sure.--Gail ShawSQL Server MVP |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-04-16 : 13:27:50
|
| I completely agree with Gail. I deleted an index a while back that showed 0 for reads and practically took down production when a monthly job ran and did a table scan on a very large table (a couple hundred GB). CPU % was at a constant 100% until I added the index back. Make sure you run the DMV query after the server has been up for a while and covers all non-regular queries/reports.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
|
|
|
Would you delete any of these indexes?