Re: Upgrading from 7.31 to 9.3 - storage requirements

First of, when we went through this process we did dbexports and dbimports to be able to come over clean. The time for an upgrade in place depends upon the number of databases and tables and we had lots. The algorithm approach can be a little tricky. We had a lot of small tables where data and the five (yes, five) indexes all fit within the initial extent of 32K. If you go with the default, detached, you now end up with six "tables", each at 32K (one for the data, five for the indexes.) Are those 32k extents close to empty - you bet - but the space is used. On the flip side, we had large tables with only one or two indexes so there is very little net effect Using the "space is cheap and getting cheaper" philosophy and not wishing to perform calculations against each of 400 tables (times 150 databases) we swagged it at 50% and justified it with room for growth. Fred Prose Arizona Supreme Court