Schema design question

  • Hi!

    I have asked this question in forms including this one for well over a year knowing that i was working up to the point that i would need to know this.. And i am to this point now and i still do not have an understanding of how to design the portion of my schema for a W x H = Cost schema.

    I am in BIG TIME need to get this resolved extreamly quickly.

    Can someone please help me with this..??

    Here is a link that show what i am needing..

    You will see four dropdownlist boxes. Width x Height = Price

    Any help at all will be great!

    Someone suggested to me a Matrix table but i have no idea what that is..

     

    http://blinds.com/control/product/productID,8253 

     

    SOS

    ERIK

    Dam again!

  • There are a couple of ways to do this;

    1. Have every available whole number width and every available whole number height associated with a price. Either have every available width and height entered for every available blinds or have a base price entered for every width and height and then a markup value (either flat or percentage) entered for each blinds.

    Your tables:

              Products          .

    ProductID int primary key not null (identity or some other unique ID)

    ProductName varchar (or some other textual data type) not null

    OtherProductFields

              Heights         

    HeightID int primary key not null (identity or some other unique ID)

    ProductID int not null foreign key references Products(ProductID)

    HeightValue int not null

    HeightPrice int not null

              Widths         

    WidthID int primary key not null (identity or some other unique ID)

    WidthValue int not null

    WidthPrice int not null

     

    2. Use fields to calculate everything needed.

              Products          .

    ProductID int primary key not null (identity or some other unique ID)

    ProductName varchar (or some other textual data type) not null

    OtherProductFields

              PriceSchemes          .

    PriceSchemeID int primary key not null (identity or some other unique ID)

    MinimumWidth int not null

    MaximumWidth int not null

    WidthIncrement int not null default(1)

    MinimumHeight int not null

    MaximumHeight int not null

    HeightIncrement int not null default(1)

    MinimumWidthPrice int not null

    MaximumWidthPrice int not null

    WidthPriceIncrement int not null

    MinimumHeightPrice int not null

    MaximumHeightPrice int not null

    HeightPriceIncrement int not null

              ProductPriceSchemes          .

    ProductID int not null foreign key

    PriceSchemeID int not null foreign key

    CONSTRAINT [PK_ProductPriceSchemes] PRIMARY KEY CLUSTERED (ProductID, PriceSchemeID)


    My blog: SQL Soldier[/url]
    SQL Server Best Practices:
    SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • Just to let you know that i did recieve your response the other day and i am egear to start working with your example... I am strapped to a GUI right now and i am going loco. I might have a question or two in a couple of days or a week..

    Thanks again

    Erik

    Dam again!

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply