Larry, I have a utility on one application that allows the system administrator to PACK INDEX when needed. This utility is used whenever indexes appear to be acting up, but it is not very often. Yesterday, I had to do some maintenance and I decided to RELOAD the database which effectively packs it and the results are:
OLDPMSDB rb1 108460 6-23-09 5:28p OLDPMSDB.rb1 OLDPMSDB rb2 187670528 6-23-09 5:28p OLDPMSDB.rb2 OLDPMSDB rb3 551726592 6-23-09 5:28p OLDPMSDB.rb3 OLDPMSDB rb4 30547968 6-23-09 5:28p OLDPMSDB.rb4 PMSDB rb1 105400 6-24-09 12:30a PMSDB.rb1 PMSDB rb2 196575232 6-24-09 12:30a PMSDB.rb2 PMSDB rb3 63610880 6-24-09 12:30a PMSDB.rb3 PMSDB rb4 30547968 6-24-09 12:30a PMSDB.rb4 As you can see, the results are eye-popping! By the way, this is a compiled 7.5 application. Javier, Javier Valencia 913-915-3137 ________________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Wednesday, June 24, 2009 12:22 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Pack Index and RB3 file size. Hi all. I have an application in which I'm getting occasional weirdness in the indexes for one particular table, leading to incorrect results on some queries. I've been able to fix this with other users on-line by using the PACK INDEX <IndexName>. It's a big help to be able to do this with users in the system. Unfortunately, that only helps me AFTER the users have experienced and noticed the problem. I'm thinking of implementing an automatic PACK INDEX routine to run at night to catch these things in advance. This database runs 24 hours, but it's less busy at night. My only concern is that by rebuiling these indexes repeatedly, my #3 file will grow in size. Does anyone have experience with this? Is that what happens? Or does R:Base somehow recycle the space currently used by an index? -- Larry
