Re: "Nologging"-option tablespace and tables

Jens Mueller wrote:

> He Jan,
>
> thanks for the answer.
>
> The reason why I asked is, that we have an application, where not
> every data must be written to the redo. This are some session-handling
> tables, temp-tables etc. These table dont cover an important data.
> So the question for us is:
> Do we have to create an extra-tablespace with nologging-option (and
> move the tables into that new tablespace) or is enough to disable this
> option at the table itself?
>
>
> Jens

Hi!

when the table is in nologging mode only the first statment is not logged.

example
create table test nologging as select * from all_objects;

The records inserted in this statement will not be logged. But all inserts to the table after that _will_ be logged.

When you set nologging in the tablespace you do not have to explicit type nologging in the create table statement. Its the default.

The importat issue here is....

Do you have a performace problem?
If not. Why try to fix something that is not broken? I dont think the small amount of data you save in a table for session handeling and temp data is the problem if you do have performance problems. (its a gut feeling, i dont have enough info)

If you have some session data that only is relevant to that specific session you might think of using a global temporary table (and set it to "on commit presereve rows").

Hope it helps.

Regards,
Janne!

Disclaimer:
The above are the opinions of God as recited by my telepathic goldfish. Those who oppose them with be struck by lightning. Such an event will be reflected on their electrical bill. Received on Wed Nov 19 2003 - 10:04:52 CST