Hi,
I am not sure if I have a solution for you, but I have a number of questions:
1) just for my interest, what type of application would need to insert 3-4 million records per hour?
2) Why does the application need to do the select count(*)....? What verification is being performed?
3) Perhaps the design of the application could change so the number of records is reduced?
Cheers,
Craig.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Friday, 20 September 2002 9:53 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: count(*)
Paula et al:
It could work if the analyze is done after the load using DBMS_STATS. Then
the num_rows would be accurate. With the monitoring turned on , analyzing
would be done on the
table if more than a certain percentage had changed. It is not an elegant
solution. A more pratical one , if you're using SQL Loader, is to use a
counter variable. If not using SQL Loader, then a synthetic key backed with
a trigger and sequence, could suffice. It could give you the accurate
count after a load by checking the NEXTVAL.sequence_name or
CURRENTVAL.sequence_name. The method could be put in a procedure to
improve efficiency.
Just a thought.
RWB
