Re: Procedure to DROP a 700 GB Table in 10gR2 ?

I can't think of a valid reason to truncate before dropping. I would just drop the table, and yes you'll have to cascade constraints or it will fail. Just make sure that you're ready for those constraints to be dropped.

Don.

On 1/22/07, VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com> wrote:
>
> Folks
>
>
>
> In a 3 TB TEST Database in 10gR2, a 700 GB Table needs to be DROPPED.
>
>
>
> This Table is present in a Unique Tablespace.
>
>
>
> Which of the following Options is Most Advisable w.r.t. performance, speed
> & ease of Drop:-
>
>
>
> 1) DROP the Respective Tablespace including contents
>
> 2) Truncate the Table -> Drop the Table
>
> 3) Drop the Table
>
> 4) Some Other Option?
>
>
>
> Thanks indeed
>
>
>
>
>
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> solely for the use of the addressee(s). If you are not the intended
> recipient, please notify the sender by e-mail and delete the original
> message. Further, you are not to copy, disclose, or distribute this e-mail
> or its contents to any other person and any such actions are unlawful. This
> e-mail may contain viruses. Infosys has taken every reasonable precaution to
> minimize this risk, but is not liable for any damage you may sustain as a
> result of any virus in this e-mail. You should carry out your own virus
> checks before opening the e-mail or attachment. Infosys reserves the right
> to monitor and review the content of all messages sent to or from this
> e-mail address. Messages sent to or from this e-mail address may be stored
> on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>

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