No 1) is the latest utility supplied by Oracle and so would seem to be = the best one to start with. However this is very easy to test yourself, just set autotrace on, run = all 3 commands on a schema with a variety of different sized tables (and then report on what you have found) I think locking issues may come into play, especially with the Analyze = table command John -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Seema Singh Sent: Thursday, December 23, 2004 8:06 PM To: oracle-l@xxxxxxxxxxxxx Subject: Which one is good in terms of performance Hi, 1) exec dbms_stats.gather_schema_stats(ownname =3D>'''||username|| ''',degree=3D>4,cascade =3D>TRUE,options=3D>''GATHER STALE''); 2)DBMS_UTILITY.ANALYZE_SCHEMA('USERNAME','COMPUTE'); 3)ANALYZE TABLE <TABLENAME> COMPUTE STATTISTICS FOR ALL INDEXES COLUMNS; Please suggest which is best in case of cost based optimizer in = Oracle9i. thanks -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l