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 |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2005-03-31 : 07:18:30
|
| Can anyone attempt an explenation to show roughly at what point a database would have too many indexes - which would have an effect opposite to the desired one by actually slowing things down.How/why does that happen? Is it because of the extra space being taken up? Is it because SQL Server takes longer because it has more indexes it has to choose between and compare? What's the story? |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-03-31 : 07:25:58
|
| "Too many indexes" is not a fixed value really. Having lots of indexes should increase read performance, but can negatively affect write performance as each write may result in an index change.-------Moo. :) |
 |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-03-31 : 07:29:27
|
| My understanding is that too many indexes could actually have a negative impact on read performance. There is a "optimal stage" that you can pass. After that you start slowly declining again. |
|
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-03-31 : 08:55:07
|
| Am I talking nonsense or is there such a point? |
|
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-04-01 : 02:38:05
|
| Nobody knows... |
|
|
|
|
|
|
To many indexes