Dan,
An index should be assigned to the single column as well, as long as
the values are fairly unique. If there is a WHERE Clause used in the
application, there should be a matching index, single column or
multi-column, with the matching ascending/descending index order
following the ORDER BY.
After the index is created, review the "Duplicate Factor" value in
the Data Designer interface. If the value is relatively small when
compared to the number of rows, the index will boost the performance.
Otherwise if the Duplicate Factor value is high and close to the
number of rows, delete the index as there would not be a speed improvement.
Razzak
At 11:36 AM 10/22/2021, Dan Goldberg wrote:
I have unique key on 2 columns in a table.
I also do a lot to lookups using one of the columns that are in that
unique key.
The question is: should I do a index on the one column as well or
does the unique key create index for each of those 2 columns?
TIA
Dan Goldberg
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/0LwJuC-1mks913t0w-0183oy%40mrelay.perfora.net.
