Karen
I will give that a try.
Marc
----- Original Message -----
From: [EMAIL PROTECTED]
To: RBASE-L Mailing List
Sent: Monday, November 24, 2008 10:40 AM
Subject: [RBASE-L] - Re: Which method is best?
Marc: I definitely agree with Dennis. I always drop and recreate the temp
table every time I need it. Back in 6.5 days, one client had some old code
where they ran a big batch processing file overnight. The code would delete
rows from the temp table through a cursor process. The temp file created got
so huge that it actually filled all the available drive space! We couldn't
figure out why the program kept failing. That was in 6.5, but I imagine it
could still happen in current versions.
Karen
If you have SCRATCH set to a local drive then Temp tables are stored
locally and are very fast.
I recommend using indexes (create after populating a table) because this
makes them even faster and more robust.
Instead of Deleting all rows from a temp table, drop the table and recreate
it.
This will prevent the temp file from growing through the day.
Most databases grow in file size when records are added, but do not shrink
when record are deleted.
This is true also of temporary tables.
I suspect your main slowdown issue is the growing scratch file size.
Dennis McGrath
