Design

Hello all,

I am trying to correctly model the relationship between products and
versions within my db. The problem I have is how to store the version
data. I need to collect the following information:
1) Major Build Number (int)
2) Minor Build Number (int)
3) Build Number (int)
4) SP number (int)

What is the "correct" schema for this? How many tables and what
columns?

(On a side note if any one has any links to useful examples of DB
design could they post them?)

Thanks,
JoseHi

The way you design your tables will depend to some extend on if you want to
do with them. If you will need the query the constituent parts, then holding
them separately is an option. If you don't then you may want to hold it as a
single string. You may want to be more exact with your datatypes. Tinyint
may be sufficient for your purposes and smallint almost certainly will.

You may want to check out the chapter on Database Design Considerations in
Books online.

John

"Jose Perez" <jlpv@.totalise.co.uk> wrote in message
news:3724a9d9.0412280740.4bfe3dfa@.posting.google.c om...
> Hello all,
> I am trying to correctly model the relationship between products and
> versions within my db. The problem I have is how to store the version
> data. I need to collect the following information:
> 1) Major Build Number (int)
> 2) Minor Build Number (int)
> 3) Build Number (int)
> 4) SP number (int)
> What is the "correct" schema for this? How many tables and what
> columns?
> (On a side note if any one has any links to useful examples of DB
> design could they post them?)
> Thanks,
> Jose