My table strategy involves a main table for registered users.
This table as it works out has a primary index (auto increment) and approximately 6 foreign key columns. All linked column values require three-way and four-way joins to print their values.
How can I balance the "memory required for indexed columns vs. process speed"? (Designing with a combination of single and composite indexes, assuming this can be done.)
Is creating an index really worth it if there will be many inserts?
What about if not many updates or deletes but many selects?
Can do these to test, but where do I get actual time figures from?:
SELECT /*+ FULL (table)*/ col1, col2 FROM table: //full scan
SELECT /*+ INDEX (table indexname)*/ col1, col2 FROM table: //index