>
> is there a guildeline to what constitutes over indexing?    5, 10, 15, +
> indexes on a table?
>
>
>
>

"Kalen Delaney" <replies@public_newsgroups.com> wrote in message
news:uLNxbs9NGHA.2628@TK2MSFTNGP15.phx.gbl...
>
> Hi g
>
> SQL Server allows you to create up to 250 indexes on a table, so you're
> not even coming close. :-)
>
> Overindexing means that the cost of the indexes outweighs their benefit,
> and you can only determine this by testing.
> For a read only table, lots of indexes could be a good thing, as long as
> you have the disk space available.
>
> For a table with heavy updates, you have to keep in mind that every index
> needs to be maintained for every insert, every delete, and most of your
> update operations. Plus you might need to be concerned with fragmentation
> and might have to plan for time to rebuild the indexes to remove
> fragmentation.
>
> You need enough indexes to support finding the data you need, but not so
> many that data modifications become unacceptably slow.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
>
> "g" <gregoranton_nospamplease_@hotmail.com> wrote in message
> news:7l1Lf.7454$Nr5.4059@clgrps13...
>>
>> is there a guildeline to what constitutes over indexing?    5, 10, 15, +
>> indexes on a table?
>>
>>
>>
>>
>
>
>