Re: How many is too many

Toon

You are correct. There are about 70,000 tables owned by the application
schema. I see one Primary key (not sure how it got there :)) and one unique
key constraint owned by that user with no foreign key at all.



On Fri, Aug 12, 2011 at 12:23 AM, Toon Koppelaars <
toon.koppelaars@xxxxxxxxxxx> wrote:

> Tables with that many indexes, to me, are usually a strong sign that the
> table holds multiple 'entity types', and in fact should have been designed
> as multiple tables. I bet that there are a lot of NULL-able columns in that
> table too, right?
>
> The fact that you mention 'third party product', by the way, is a sign in
> that direction too :-)
>
>
>
> On Thu, Aug 11, 2011 at 10:45 PM, Ram Raman <veeeraman@xxxxxxxxx> wrote:
>
>> Listers,
>>
>>   I am looking at a table in our system and it has 12 indexes, we are
>> planning on adding another one. I am aware of the effects of having too many
>> indexes, but in this case adding an extra index helps a certain query that
>> runs slow. Other queries and most other operations against the table
>> are acceptable too. I see a few tables like this; is there a number above
>> which is considered a no-no when it comes to adding more indexes.
>>
>> PS. The tables and queries are structured in a way that seem to require
>> several indexes - it is a third party product.
>>
>> TIA,
>> Ram.
>>
>
>
>
> --
> Toon Koppelaars
> RuleGen BV
> Toon.Koppelaars@xxxxxxxxxxx
> www.RuleGen.com <http://www.rulegen.com/>
> TheHelsinkiDeclaration.blogspot.com<http://thehelsinkideclaration.blogspot.com/>
>
> (co)Author: "Applied Mathematics for Database Professionals"
> www.rulegen.com/am4dp-backcover-text
>
>

Other related posts: