Database Design
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Database Design

  1. #1
    Join Date
    Nov 2000
    Posts
    34

    Arrow

    Hi Friend,

    I am having question about database design.
    Here we wil have database size of 4 tb. This database
    performs only inserts and select operation. No update is going to occur. I am plannig to desgin one huge table of 82 fields
    and going to partition and index it on 16 different columns.
    We r using oracle 8i (8.1.6) and Sun solaries 2.8 on sun E6500
    machine.

    But my colleagues suggest me to go for more than one table and use joins while query
    instead of one huge table.While one huge table is possible.

    So what will be the best database design to get optimal
    select query performance.

    Thanks
    Jayesh

  2. #2
    Join Date
    Sep 2000
    Posts
    384
    1.)In that case what will be the average row size...
    2.)how big will be that table..

    pls inform..
    Radhakrishnan.M

  3. #3
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,095
    I personally prefer one large table with multiple partitions distributed on many disks.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  4. #4
    Join Date
    Sep 2000
    Posts
    384
    Your have decide purely from the application angle.

    Incase you need only columns always and the rest very rarely.Because of this you will fill the buffer with unwanted buffers for a longtime . and you need to have many i/os .

    then in that case it is better to denormalize the table.


    Radhakrishnan.M

  5. #5
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,136
    JOIN in Oracle is a costly resource. Hence , one table with 82 columns design is good. Besides, if the columns do not have value, nothing will be stored. This will save your disk space.

  6. #6
    Join Date
    Jun 2000
    Posts
    417
    To what extent is everything (de)normalized when it is all in one table? If one table with 82 columns is fully normalized then of course that's the way to go.

    If it's not, as pointed out by the others one big table might still be the way to go but at some point you might want to consider normalizing and creating more tables if the application requires it. You might not want one huge inflexible table if your application has to extend in the future.

    Try to learn about the application and what is being stored in those 82 columns and you can make a better decision.

  7. #7
    Join Date
    Jan 2001
    Posts
    1

    Wink About table normalizaton...

    Hi Jayesh,

    I too feel keeping data in one table will be suitable. As u know normalization is a good thing but it was very strongly practiced in the old days when memory and hard disk were very costly, seeing the latest trends in market, I personally feel, people go for HARDWARE TUNNING rather than SOFTWARE TUNNING as now memory and harddisk is not a problem. So you can have a bit denormalized table .NO HARM.

    Regards
    Deepankar


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