Page 4 of 4 First ... 234
  • Jump to page:
    #46
  1. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2003
    Location
    Yucatan, Mexico
    Posts
    5
    Rep Power
    0

    Normalize / Denormaliza


    We have a database of about 600,000 live (active) items.

    So far each item has one and only one price at which it is sold.

    SOME items (not all of them, a minority) will eventually sell at different prices in SOME stores.

    I suggested to add a table:

    iditem
    idstoretype
    price

    If the idstore/iditme combination is NOT FOUND, then the selling price for this item is the one already stored in our 600,000-item table it the "price" column.

    Another persons suggests that we should create a table:

    iditem
    idstoretype
    price

    And add there all 600,000 items for the time being. If prices change for another store, then, all 600,000 rows of the new

    iditem-idstoretype-price

    should be inserted, even though 98.5% of all rows will have exactly the same price for the same combination of IDITEM-ITSTORTYPE.

    How should this be managed?

    Thank you for any advise on this.
  2. #47
  3. No Profile Picture
    Ducani
    Guest
    Devshed Newbie (0 - 499 posts)

    An Introduction to Database Normalization


    An Introduction to Database Normalization

    A database can be great fun, right? Yes, of course! There are though, a couple things that can ruin all that hard work and effort you put into your efficient little database. Today we discuss how to keep that beloved bin of data from going bad on you: database normalization.

    Please discuss this article in this thread. You can read the article here .
Page 4 of 4 First ... 234
  • Jump to page:

IMN logo majestic logo threadwatch logo seochat tools logo