vertical partitions
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: vertical partitions

  1. #1
    Join Date
    Jan 2002
    Posts
    78
    Hi All,

    I have a very large table ( Row wise and Column wise). I already implemented horizontal parititioning ( range) on this table. Now I am looking to get information how to implement vertical patitions on this.

    For Example,

    Table Name : table1 having four columns

    col1 col2 col3 col4 col5 .

    Now i am planning to put col1 and col2 in one tablespace and col2 and col3 in another tablespace. But for the developer the table should be appear as one table.

    Please help me in this regard.

    Regards
    Sekhar

  2. #2
    Join Date
    Apr 2002
    Posts
    135
    simple use views
    Good Judgement comes from Experience.
    Experience comes from Bad Judgement

  3. #3
    Join Date
    Jan 2002
    Posts
    78
    views are different. My problem is not to use views. I am looking to port one table onto multiple tablespaces. Is it possible ??

    Originally posted by sona
    simple use views

  4. #4
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    hash partitioning, you cannot control what data goes to what tablespace. Oracle decides it by using a hash function

  5. #5
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Originally posted by Sekhar
    Table Name : table1 having four columns

    col1 col2 col3 col4 .

    Now i am planning to put col1 and col2 in one tablespace and col2 and col3 in another tablespace. But for the developer the table should be appear as one table.
    This requirement has nothing to do with any kind of Oracle's partitioning (hash, range, list). In fact this is not possible unless the table is IOT (index organized), where you can define columns col3 and col4 to be stored in an "overflow segment" of IOT, which can be located in other tablespace than your "index portion" of the same row (col1 and col2).

    The only other sollution would be to split your table into two separate tables that would both contain your current primary key columns and present those two tables to your developers as an equi-join view of those two new tables.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  6. #6
    Join Date
    Apr 2001
    Posts
    219
    If each column was a LOB you could store it in its own tablespace, right?
    ______________________
    Applications come and go,
    but the data remains!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width