ron
Member
Our main db is 110GB. It was dumped/reloaded last December and last April under Progress 8.3E. Each time the DB shrank by about 8 GB ... and regained this 8 GB within three weeks as indexes lost their high degree of compression. (All normal.)
On 18th May we upgraded to 9.1D05 (last week to 9.1D06) - splitting the whole DB into eight Areas. Three Areas contain indexes only ... for the largest tables we have.
Since converting to 9.1D the DB is growing at an alarming rate; it is now 13.4 GB larger than when converted. In the same period after the prior two D&L's it grew 7.6 and 6.1 GB. ALL of this excessive growth is within the Areas that contain indexes.
Has anyone else seen a similar effect?
Does anyone know what causes this?
Regards,
Ron.
On 18th May we upgraded to 9.1D05 (last week to 9.1D06) - splitting the whole DB into eight Areas. Three Areas contain indexes only ... for the largest tables we have.
Since converting to 9.1D the DB is growing at an alarming rate; it is now 13.4 GB larger than when converted. In the same period after the prior two D&L's it grew 7.6 and 6.1 GB. ALL of this excessive growth is within the Areas that contain indexes.
Has anyone else seen a similar effect?
Does anyone know what causes this?
Regards,
Ron.