What you describe can certainly happen.
There are some techniques you can pursue to alleviate this:
1) Have a nightly defrag process. This won't help if you calc five times a day, but if it's only once, you're in the catbird seat.
2) Do you really need a CALC ALL? Maybe only portions of the db need to be aggregated -- a focused aggregation at least will fragment less of the database.
3) What about Intelligent Calc. If done correctly, this can just affect the blocks that need to be aggregated, thus cutting down on the bits of data that haven't changed.
4) Consider ASO -- if your calculation is just CALC ALL it is possible that your database is just a rack and stack db that just aggregates data (okay, and does a little more, ASO is getting more and more functionality). There is no *data* fragrementation issue with ASO (or not an appreciable one -- we're talking angels on the head of a pin wrt slices) although there are issues around the *outline* getting fragmented.
Regards,
Cameron Lackpour
|