Re: Reorganizing the DB.. the tricky way

From: Richard Foote <richard.foote_at_bigpond.com>
Date: Mon, 7 Apr 2003 23:30:14 +1000
Message-ID: <5Ueka.9034$1s1.158691@newsfeeds.bigpond.com>

"Rick Denoire" <100.17706_at_germanynet.de> wrote in message news:0iu09vguedtcbee4e347kgm0jh60dck2ph_at_4ax.com...
> DA Morgan <damorgan_at_exxesolutions.com> wrote:
>

< snip>

> If developers need a new index, and I told them to use a specific
> tablespace to acommodate that index, how are they going to get that
> done without explicitly putting the name of the tablespace in the SQL
> statement? So you say that is wrong. You are surely more experienced
> that I am, so please let me know how to do it the right way.
>

Hi Rick

Unless we're talking a "play" sandbox database where performance is not really of concern, I would question developers creating any objects as such. In any "production" level database, the DBA should really be creating all objects to ensure that basic tuning and capacity management issues are considered.

When developers create a "new index", do they understand and consider appropriate pctfree, inittrans/maxtrans, buffer pools, freelists, partitioning, local/global, no/logging, no/compress, statistics, bitmap, etc. ? Do they appreciate I/O balancing or storage/capacity management, etc...

Make sense ?

Cheers

Richard Received on Mon Apr 07 2003 - 08:30:14 CDT