RE: Dropping Tablespaces - All Nighter

On Mon, 31 Jul 2000, you wrote:
> Hi Kirsten,
>
> If the problem is large numbers of extents in some segments,
> then it may be quicker to take a full database export and rebuild the
> entire database.

Define 'large number of extents'. The most I have ever seen was ~400,000 extents in a tablespace. We inherited the database in rough shape - the database was originally a straight port from db2, where, apparently, taking defaults for tablespaces and have each table/table partition/index/index partition in its own tablespace is fine. When we took over from $OTHER_COMPANY, the database had in excess of 700 tablespaces, 800 datafiles, and defaults all over the place for very large tablespaces - initial 64k, next 8k for 20GB tables. Needless to say, 100,000 extents per tablespace was very common :(

Anyone else with a similar horror story?

Cheers,
GC
 --
I love the way Microsoft follows standards. In much the same manner that fish follow migrating caribou. Received on Mon Jul 31 2000 - 18:32:22 CDT