By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,412 Members | 1,630 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,412 IT Pros & Developers. It's quick & easy.

Design

P: n/a
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
Jul 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi

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" <jl**@totalise.co.uk> wrote in message
news:37**************************@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

Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.