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. 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.
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS 66062-4571 (913)829-0888 (913)649-2904 FAX -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Emmitt Dove Sent: Monday, January 27, 2003 12:32 PM To: RBASE-L Mailing List Subject: [RBASE-L] - runaway file 3 size All, I have a problem that I hope someone might be able to illuminate. At two locations we are running our app under 1.863 Windows. After a fresh unload/input, the file 3 size will be approximately 63% of the size of file 2. However, file 3 starts to grow. After 9 days at one location it is now 300% the size of file 2. If left unchecked, it will continue to grow. The dimensions of the database are: 239 Tables 73 Views 2,244 Columns 544 Indexes/Keys 32 SATTACHed tables with 553 columns This behavior has been present at one location for several months, dating back to Inline Patch 2 days. I recently added about 15 tables to the other location and converted everyone to IP3, and the growth started there also. I do not think this is version-specific. There is something else causing the runaway growth in file 3. Any clues? Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT 06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED]
