Database Tidy-up

Hi, We have several production systems running the same DB (OnLine 7.22). All sites want their databases to be 'tidied up' every 3 or 4 months. Essentially this means archiving old data and refreshing the tables. For each site I thought about dbexporting to disk, dropping the database, recreating it, reloading the data, doing an UPDATE STATs, etc, etc. Not each site has a tape drive, and I shall be doing all this remotely. The problem is that the hard drives for each server are at 75% of capacity, so I have no place to store the unload files (purchasing new HDs is not an option). I believe that removing old data will make the table unloads small enough to store on the drives. There is the option of copying unloads to my local HD across the WAN (ugh!). So, I've decided to do each table in turn (unload, drop, create, reload, create indexes, update stats, next table...). My question is ... Is it worth doing this? Will the sites see any performance gain? The newly created tables will still be fragmented accross DBSpaces (other tables will be sitting in the middle of the DBSpace, forcing the new table to be created around them). Should I really aim to drop the entire DB, then recreate it and reload? ANY suggestions are VERY welcome!! TIA. -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading