Quote:>We have a DBA in the office, however, who tells me I'm an idiot
Us DBAs are good at that :-).
>this since I'll fragment the tablespaces, and that I should truncate the
>tables instead. Unfortunately, he is unable to articulate why this would
Offhand, I'm not convinced that this is true, though it
might be. Consider that the first time through, you created
the tables and populated them with data. Dropping and
recreating the tables, and repopulating them, should yield
more or less the same results the second time as the first.
If you were truly worried about fragmentation, you would
check the max size of the tables after populating them, and
then recreate them once with an initial extent of that size.
Quote:>I haven't seen any performance degradation or encountered any problems with
>creating new extents, so I'm a bit skeptical.
Then don't worry about it. I spend my time chasing problems
that bother my users, not the theoretical things. Well, I
chase the theoretical things too, but they are much lower
down on the priority list. I think fragmentation is
overrated as a problem, and that people worry about it more
than they should.
If you do want an idea of how badly fragmented things are,
you can query the dba_extents view (you may have to use
all_extents or user_exents) like this:
This will give you a count of the number of extents that
exist for a table. If it's only a half-dozen or so, don't
worry about it. If you have 500 extents, then you should
probably do something about it.
p.s. why isn't your DBA helping you on this?
Brighten the Corner Where You Are