Re: performance of recreate oracle user Vs drop objects

Hi!

If you only import data and the data structure remains the same, you could just truncate tables and load data into them. But it has it's own problems, if you are importing large data sets, then load is slower because indexes already exist on table (import creates indexes after data load). Also you might have constraint issues (might have to disable them prior to load).

If you don't want to mess around with above then the preferred method for me would be dropping all the objects under a user. But (there's always a but) if you're very lazy, then it's easier to drop user with cascade and recreate it, instead of creating a script for dropping all objects.

Tanel.

"Srinivas" <ps_chowdary_at_hotmail.com> wrote in message news:68dbad24.0307291146.204216ce_at_posting.google.com...
> In our system we need to handle large number of oracle users. Each
> oracle user holds one instance of user datasets. To support
> loading/archiving operations we need to export and import data into
> these oracle users.
>
> My question to you is before importing the data is it
>
> 1) better to delete and recreate the oracle user
>
> or
>
> 2) just drop all the objects in the oracle user
>
> thanks,
> Srinivas
Received on Tue Jul 29 2003 - 16:42:35 CDT