RE: Best Practices for Partitions ?

From: VIVEK_SHARMA <VIVEK_SHARMA_at_infy.com>
Date: Mon, 19 Feb 2001 04:48:12 -0800
Message-ID: <F001.002B7CEF.20010219042023@fatcity.com>

Mark,

Thanks Indeed for responding

My Replies(ANS.) are Given Below your Questions in CAPITALS :-

        -----Original Message-----
        From:   Mark Leith [SMTP:mark_at_cool-tools.co.uk]
        Sent:   Friday, February 16, 2001 5:30 PM
        To:     Multiple recipients of list ORACLE-L
        Subject:        RE: Best Practices for Partitions ?

        Vivek

        Take a look at Steve Adams' site here

        http://www.ixora.com.au/tips/design/partitioning.htm

        It gives some good advice when considering partitioning, which I
infact read
        through this morning.

        Composite or Range? 
        ANS. ALL TABLES PARTITIONED BY RANGE

        Well, what kind of data does this table hold, 
        ANS. WE ARE CONSIDERING PARTITIONG ALL THE 400 TABLES BASED ON

PARTITION KEY "BRANCH_ID"

        DISTRIBUTION OF DMLs :-
        PRIMARILY INSERTS & SELECTS 
        UPDATES - RELATIVELY SMALL
        DELETES - NEGLIGIBLE

        NOTE - THIS BEING A BANKING APPLICATION . VARIOUS BRANCHES OF A BANK
SPREAD ACROSS THE COUNTRY 
        LOG INTO THE CENTRALISED DATABASE .

        what are you trying to achieve from a partitioned table? 
        FOR OPS WE ARE PARTITIONING THE DATA TO PREVENT CONTENTION AS THE 2
INSTANCES WILL ACCESS 
        DIFFERENT PARTITIONS BASED ON "BRANCH_ID" . 
        OPS BEING CONSIDERED PRIMARILY FOR SCALABILITY .

        QS. WHICH INDEXES ARE ADVISABLE IN SUCH A SCENARIO , LOCAL OR GLOBAL

        It more depends on the
        nature of your DATA.

        Steve's jist, is that if you have a table partition, you should also
have an
        index that refers to that table partition, as this will also help
with
        maintenance operations etc. If you have an index for the partitioned
table
        as a whole, and decided to reorg one partition, which could be old
data,
        then you would also have to reorg the entire index - which could
result in
        user problems. If you have a partition specific index, you could
just reorg
        each specific partition without affecting performance on the whole.

        Correct me if I'm wrong Steve..

        Regards

        Mark

        -----Original Message-----
        VIVEK_SHARMA
        Sent: Friday, February 16, 2001 06:40
        To: Multiple recipients of list ORACLE-L



        Qs. Are Composite Partitions Better than Range partitions as a
General rule
        ?
        OR is it dependent on Nature of Business/Application ?

        Qs. For Tables which are partitioned , is it advisable to Partition
their
        Corresponding Indexes Also with the Same Respective Key Values List

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: VIVEK_SHARMA
  INET: VIVEK_SHARMA_at_infy.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 Mon Feb 19 2001 - 06:48:12 CST