Thanks.


>>I wouldn't know what to test, just wanted to know if someone can tell me why I should have an index under those circumstances as of now I'm not putting an index on that table.
>>
>>If you meant test for speed then I guess I could test for that, I don't think I will see any major difference
>
>Assuming your records aren't some huge structures, and assuming you aren't doing this with hundreds of tables all actively being accessed at once, then you can assume the table data will get cached into memory and you will have fast performance with or w/o indices. This is also assuming your application isn't already starved for memory.
>
>>
>>
>>>>Hello all,
>>>>
>>>>Is there a good reason to put an index on a table with few records, lets say max 100 records? Free table, no need to check for duplicates or referential integrity.
>>>>
>>>>Thanks.
>>>
>>>There's only one way to find out; test it.