Subject | Maintenance of temporary tables |
---|---|
Author | Jerome Bouvattier |
Post date | 2004-06-22T13:31:58Z |
Hello,
I'm using a fake temporary table to hold lists of IDs. It has two fields :
LISTID and ID.
The common scenario is that I insert records in this table at the start of a
tansaction and delete them all when committing, so that the table always
"looks" empty.
I expect to insert and delete at most 300000 rows a day (10 consecutive days
per month).
What kind of issues should I expect and how should I prevent them ?
Some ideas ...
Should I issue a "Select count(*)" every once in a while during the day to
take care of GC, or should I leave that up the nightly SWEEP ?
Should I delete rows during production at all, or instead leave that up to a
nightly bulk_deletes_task ? (The table has a unique compound index, so I
think it shouldn't introduce to much performance penalty)
Or ?
Thanks for your help.
--
Jerome
I'm using a fake temporary table to hold lists of IDs. It has two fields :
LISTID and ID.
The common scenario is that I insert records in this table at the start of a
tansaction and delete them all when committing, so that the table always
"looks" empty.
I expect to insert and delete at most 300000 rows a day (10 consecutive days
per month).
What kind of issues should I expect and how should I prevent them ?
Some ideas ...
Should I issue a "Select count(*)" every once in a while during the day to
take care of GC, or should I leave that up the nightly SWEEP ?
Should I delete rows during production at all, or instead leave that up to a
nightly bulk_deletes_task ? (The table has a unique compound index, so I
think it shouldn't introduce to much performance penalty)
Or ?
Thanks for your help.
--
Jerome