Part of our billing process creates over 1 million inserts into a
table which kills our redo logs. Then when the process is complete
the data is extracted and never referenced again. We truncate the
table each night. In other words the data is semi-temporary.
I'd change the table definition to a temporary table, except that if
the program crashes it needs to pick up where it left off and not
start all over again. There has got to be another way to handle this
process, but I'm at a loss for a solution. Any ideas would be greatly
appreciated!!!
Received on Mon Oct 25 2004 - 14:50:02 CDT
