A snail going uphill through jungle vegetation? Molasses in thenorthernmost region of the Siberian tundra?Do You Yahoo!?
Yahoo! Mail Personal Address -
Get email at your own domain with Yahoo! Mail.
Turtles walking through peanut butter in January?
-Original Message-From: Chuck Hamilton
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, March 27, 2001 2:32
PMTo: Multiple recipients of list ORACLE-LSubject: Which
is faster, Metalink or...
A snail going uphill through jungle
Water flowing uphill (that never works either)
[EMAIL PROTECTED] 03/27/01 02:52PM
Turtles walking through peanut butter in January?
-Original Message-
Sent: Tuesday, March 27, 2001 2:32 PM
To: Multiple recipients of list ORACLE-L
A snail going uphill through jungle vegetation?
Metalink, hands down.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mohan, RossSent:
Tuesday, March 27, 2001 2:52 PMTo: Multiple recipients of list
ORACLE-LSubject: OFFTOPIC - RE: Which is faster, Metalink
or...
Turtles walking through
Direct patch sqlldr (and insert-append) do allow
indexes - its just that you get slugged a little more
on rollback and redo...
I don't have any metrics to compare - typical usage of
either tends be to the ol' a) drop ind, b) load, c)
redindex
hth
connor
--- Martin Kendall [EMAIL PROTECTED]
Hi Yong,
I don't think that's right. Try it on a table with no indexes, and dump
the redo and undo blocks afterwards. My tests show that there is no row
level redo (layer 11) except against the data dictionary tables for
space management, regardless of whether the table or tablespace is
defined
Hi, Connor,
The append hint to insert does not disable generating rollback info. It does
stop redo generation for a nologging table.
Yong Huang
[EMAIL PROTECTED]
you wrote:
If you're on 8.0 or higher, try
insert /*+ APPEND */
into table
select * from other_table;
where "table" is defined as
If you're on 8.0 or higher, try
insert /*+ APPEND */
into table
select * from other_table;
where "table" is defined as nologging. Then you won't
hit either redo logs or rollback segments..Its the
equivalent of a sqlldr direct load
hth
connor
--- CC Harvest [EMAIL PROTECTED] wrote: I have
Chris,
Does the destination table have to be recoverable? If not you could built the table
with the UNRECOVERABLE clause and your problem is solved.
In large inserts from one table to another for archive purposes, I get around the
large RBS problem by using a procedure with a commit every
I have the following scripts:
insert into table
select * from table2
;
So if use the about bulk statement in my
application, and the table2 is big, say 10
million records, my concern is that it's
going to fail because of the possible rollback
segments failure. So then I have to use PL/SQL
to
You can try the Bulk insert feature of Oracle. It is available from Oracle 8i
onwards. It really reduces time.
--
On Thu, 22 Mar 2001 18:35:21
CC Harvest wrote:
I have the following scripts:
insert into table
select * from table2
;
So if use the about bulk statement in my
application,
);
CONTRACT_ITEM(CONTR_I_ID,CONTR_ID,PHONE_NUM_ID);
PHONE_NUMBER(PHONE_NUM_ID,PHONE_NUM);
I have the PHONE_NUM and I need the CUST_ID.
Which Faster?
SELECT CUST_ID from PHONE_NUM,CONTRACT_ITEM,CONTRACT,CUSTOMER where [JOINS] and
PHONE_NUM=searchedone
or In procedure or function
select
to use one select with
joins?
For example:
CUSTOMER(CUST_ID);
CONTRACT(CONTR_ID,CUST_ID);
CONTRACT_ITEM(CONTR_I_ID,CONTR_ID,PHONE_NUM_ID);
PHONE_NUMBER(PHONE_NUM_ID,PHONE_NUM);
I have the PHONE_NUM and I need the CUST_ID.
Which Faster?
SELECT CUST_ID from PHONE_NUM,CONTRACT_ITEM,CONTRACT,CUSTOMER
13 matches
Mail list logo
