Index grows extremely large when table populated
Hello,
Not sure if this is the correct community to post this but didn't see another that would be better.
We have indexes that seem to grow extremely large.
The table size is relatively small:
123MB @ 800,000 rows
9 indexes, 1 unique the others non-unique
No primary key (unsure the reason why no primary key, but it appears most tables use a unique index instead of a primary key)
Trigger to get a Sequence number for the next available unique ID's. ( unique index)
Each month we have a nightly script that deletes the data for the previous year's month and repopulates the current year's monthly data.
Not sure if this is the correct community to post this but didn't see another that would be better.
We have indexes that seem to grow extremely large.
The table size is relatively small:
123MB @ 800,000 rows
9 indexes, 1 unique the others non-unique
No primary key (unsure the reason why no primary key, but it appears most tables use a unique index instead of a primary key)
Trigger to get a Sequence number for the next available unique ID's. ( unique index)
Each month we have a nightly script that deletes the data for the previous year's month and repopulates the current year's monthly data.
0