Re: Huge undotbs during insert

DA Morgan wrote:
> tim.kearsley_at_milton-keynes.gov.uk wrote:
>
> >>COPY is a dead ally, as it is going to be desupported.
> >>
> >>
> >>--
> >>Sybrand Bakker, Senior Oracle DBA
> >
> >
> > Indeed it is. But so what? It works with the release the OP is using
> > and it may do the job he requires, so who cares really?
> >
> > Regards,
> > Tim Kearsley
> > HBS Milton Keynes
>
> But So what you ask? I can think of quite a few so what's.
>
> 1. Did you use dictionary managed tablespaces in 9i?
> 2. Did you use rollback segments in 9i?
> 3. Are you still creating tables with LONG and LONG RAW?
>
> The point here is that as soon as Oracle announces deprecation of
> functionality all new work should use the newly recommended methodology.
> Not doing so is a violation of your fiduciary responsiblity and
> professional ethics. Basically what it is saying is that your personal
> convenience at a point-in-time is more important than your employer's
> need to have a system that is upgradable and maintainable.
>
> The only way a developer or DBA should make that decision ... is if the
> license cost of the Oracle software came directly out of that developer
> or DBA's paycheck.
> --
> Daniel A. Morgan
> http://www.psoug.org
> damorgan_at_x.washington.edu
> (replace x with u to respond)

What a load of fuss and palaver!!

The OP was talking about a SPECIFIC requirement. If a command will do a one-off job who cares that it is de-supported? Talking about "fiduciary responsibility" in this context is frankly ridiculous and pompous in the extreme.

And perhaps you could enlighten me as to why a table created by a COPY command is not viable in an upgraded database? The other features you mention - DMT, rollback etc. are permanent and enduring. A table created by a COPY command is a table as far as I'm aware. Or does an upgrade "know" that it was created with a COPY command and not recognise it or flag it as unusable. I think not, especially as you can pre-create the table and THEN populate with COPY.

I think you will find that the "SQLPlus User's Guide and Reference" release 10.1 includes a large section on using COPY, so Oracle have clearly not written if off yet anyway.

Get off your high horse and return to the real world, where most of us live and work. Or is this really just a feeble attempt at "revenge" because I picked you up recently on a couple of glaring inaccuracies you were promoting as "fact"?

Tim Kearsley
HBS Milton Keynes Received on Sun May 29 2005 - 17:41:22 CDT