Re: AUTOEXTEND

On non-production systems - autoextend works fine for me.

On production systems - well I'm inclined to think that you should never need it. After all, you already know roughly how and when the database is going to grow (even if its sporadic). After all, thats one of the reasons we have non-production systems - to work all this stuff out before it goes live.

If on a production system, your in a position where you're thinking: "I really don't know when or by how much this system is gonna grow by", then your customers have every right to be doubting your capacity to effectively manage that database.

Cheers
Connor

On 10/5/05, Niall Litchfield <niall.litchfield_at_gmail.com> wrote:
>
> On 10/4/05, Allen, Brandon <Brandon.Allen_at_oneneck.com> wrote:
>
> > Another disadvantage that hasn't been mentioned yet is the performance
> > impact - if a user is inserting rows and fills up the tablespace to the
> > point it has to extend, then the end user has to incur the cost of waiting
> > for the file to extend. This is avoided if the DBA anticipates the growth
> > and manually pre-extends the datafile, or adds another data file to the
> > tablespace.
> >
>

--
Connor McDonald
===========================
email: connor_mcdonald_at_yahoo.com
web: http://www.oracledba.co.uk

"Semper in excremento, sole profundum qui variat"

--
http://www.freelists.org/webpage/oracle-l