Note one caveat listed in the paper of "so long as the extents are sized as a multiple of (DB_FILE_MULTIBLOCK_READ_COUNT * DB_BLOCK_SIZE)". This can go out the window if PCTINCREASE is used. One other caveat not mentioned is potential problems in dropping the object. I seem to have a 10-watt bulb in my head dimly glowing that thinks it has to do with the recursive SQL required to manage the TS in the dictionary. Of course, this has nothing to do with COUNT(*), but thought it may be worth mentioning. Rich Rich Jesse System/Database Administrator rich.jesse@xxxxxxxxxxxxxxxxx QuadTech, Sussex, WI USA -----Original Message----- From: ryan.gaffuri@xxxxxxx [mailto:ryan.gaffuri@xxxxxxx] Sent: Monday, February 09, 2004 4:22 PM To: oracle-l@xxxxxxxxxxxxx Subject: RE: RE: Dead slow count(*) here is an old one by Gaja Vaidyanatha. He is a co-auther of perf tuning 101. http://www.quest-pipelines.com/newsletter-v3/0302_F.htm I think Niall Litchfield wrote a newer one? ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------