You should not expect to see much performance improvement, except in special cases where you can replace large deletes or loads by simpler partition operations. Your decision to use partitioning should be based on the ability to handle (i.e. DBA work) partitions separately, where you can e.g. mass delete/load, make parts read-only to reduce backup, or enable partial recovery during disk outages. Note, however, that much of this depends on your ability to partition indexes and data equivalently so that you avoid global indexes.
Sathish Tatikonda wrote: >Hi All, > >We are developing a system in which some tables in the database might be >having about 100 Million records. We are planning to use table and index >partition's as a means to improve performance. Could you please share >your experiences/views about handling such huge tables. Is this >partitioning sufficient or do we have to look in to some other means. > >It would also be of great help if you could provide me some pointers to >documents which gives some insight for handling such tables and >databases. > >thanks in advance, >Sathish. > > -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: =?ISO-8859-1?Q?Bj=F8rn?= Engsig INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
