Subject Temp Tables, DB Size etc
Author Moreno Vandelli
Introduction
We need to generate, every night, some tables with thousand
of "big varchar fields" records for thirdy part "olap" purposes.
If we do this, deleting all records and recreating them every
time, we see db's size increase day by day (at least 1GB a time).
We doesn't have the time to make a backup/sweep/restore every night.

Questions
a) If we procede in that way:
night:
use "execute statement" to drop previous temp table
use "execute statement" to create temp table
fill temp table with data
day:
select from temp table
a.1) Could we save time and avoid database's size increase?
a.2) Is it correct (and safe) to use DDL inside procedure
in this way?
b) Is there another way (ex: using FB2's temp tables) to
achieve the same results without drawback?

As usual, I'm sorry for my defective english.

Thank you in advance!