Re: When should a table be partitioned?

From: <tday6_at_csc.com>
Date: Fri, 18 Jan 2002 12:16:29 -0800
Message-ID: <F001.003F3E95.20020118095112@fatcity.com>

Where the business use of the data is such that the applications' selects can be satisfied by querying a known number of partitions (less than all partitions). Also where data can be archived partition-wise. Generally this means time sensitive data. I don't see much benefit to partitioning data when the data for a single select will span all partitions. Of course, I could be wrong there.

                    Cherie_Machle                                                      
    
                    r                    To:     Multiple recipients of list ORACLE-L  
    
                    @gelco.com           <ORACLE-L_at_fatcity.com>                        
    
                    Sent by: root        cc:                                           
    
                                         Subject:     When should a table be 
partitioned?  
                                                                                       
    
                    01/18/2002                                                         
    
                    08:20 AM                                                           
    
                    Please                                                             
    
                    respond to                                                         
    
                    ORACLE-L

We have a number of partitioned tables in a couple of existing data warehouses.
We are working on the design for a new warehouse and need to decide which tables should be partitioned.

For you folks that have partitioned tables, how do you decide which tables to
be partition? Some tables with very large row counts are obvious candidates.
If you go off of row counts solely, what is the cut-off point for where you should start
partitioning? Is there a rule-of-thumb?

I'm having difficulty with the not-as-huge, not-as-obvious candidates.

What other criteria do you use besides row-count? Perhaps archival requirements?

I guess it would depend on what you are using the partitioning to achieve. Partition
exclusion for read performance improvement or for culling off old data, etc.

Any shared insights for where to draw the line on partitioning candidates would
be greatly appreciated.

Thanks,

Cherie Machler

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: Cherie_Machler_at_gelco.com

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: ListGuru_at_fatcity.com (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).


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: tday6_at_csc.com

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: ListGuru_at_fatcity.com (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).

Received on Fri Jan 18 2002 - 14:16:29 CST