Javier,
There may be some unnecessary indexes, but not many. The indexes exist mostly for speeding retrieval of data - we do very many multiple-table selects and such.A couple of suggestion based on some similar behavior (although not that dramatic) that I observed lately. You may want to check your indexes, it seems that almost 25% of you columns are indexed, do you really need to have that many indexes? If you are doing a lot of data editing it could account for the growth in file 3 size, as it hold the indexes.
Packing indexes does not help. However, you hit upon something that Razzak just explained to me. I may owe the kitty a buck when this is done. The SATTACH command has a USING component. I took the USING component to work like it does with PROJECT or UNLOAD DATA FOR. It doesn't. USING on SATTACH specifies which column(s) to index in file 3.I wonder if the SATTACHED files are rebuilding indexes every time you login. I am pretty sure that now you can pack the indexes on your live database, what happens when you pack the indexes only? If packing the indexes helps, then you may try running a standalone command file every night that runs this command.
So, take a table with 16 columns and 220,000 rows and SATTACH it and you can imagine the impact on the file 3.
Sigh. I'll rebuild the database tomorrow and see how it goes.
Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
