Home » RDBMS Server » Server Administration » Nologging at table level
Nologging at table level [message #54162] Fri, 01 November 2002 02:26 Go to next message
Jez
Messages: 6
Registered: July 2002
Junior Member
I have created a table that I use to insert 170000 records each day via Microsoft DTS. As this caused a lot of redo logs to be generated, I changed the table to NOLOGGING and it has had no effect. There are still lots of archive logs. Why?

I don't think I can make the transaction nologging by the way.

Report message to a moderator

Re: Nologging at table level [message #54168 is a reply to message #54162] Fri, 01 November 2002 05:26 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
did you consider the indexes??(eventthough during insert, indexes are not used...)
also try to set NOLOGGING in tablespace level.(table level should overwrite tablespace level)

Report message to a moderator

Re: Nologging at table level [message #54174 is a reply to message #54162] Fri, 01 November 2002 10:12 Go to previous message
Trifon Anguelov
Messages: 514
Registered: June 2002
Senior Member
A common misconception about NOLOGGING. Only certain DML are affected by setting this clause.

DDL are not affected in any way from NOLOGGING. See the Detailed list of DML statements affected and the explanation why.

Hope that helps,

clio_usa
OCP - DBA

Visit our Web site

Report message to a moderator

Previous Topic: sql question
Next Topic: Rebuilding SYS Objects - Safe?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Dec 27 16:04:59 CST 2024
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.