Re: Procedure Performance Suggestion

Never drop if truncate will work. Or do you have no constraints, no indexes, no triggers, and no referencing objects that will become invalid?

But for 1000 rows, if you are having performance problems, there is something else very very wrong.

Daniel Morgan

R Chin wrote:

> I have a procedure that builds the SELECT and uses Native Dyn. SQL (execute
> immediate) to populate a table for report....
> 1) if the table NOT exist, do CTAS...(nologging)
> 2) if it exists, TRUNCATE it, and do INSERT...SELECT
> (table size about < 1000 rows)
>
> To get any performance gain....should I just DROP the table
> and do CTAS as opposed to #2 ??
>
> Thanks !
> Rob
Received on Fri Mar 22 2002 - 11:26:55 CST