If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > table normalization help

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-17-07, 23:48
Solidghost Solidghost is offline
Registered User
 
Join Date: Jun 2007
Posts: 4
table normalization help

Hello,
I am having trouble normalizing this spreadsheet I was given into E-R model tables. I will use Access2007 to do this, and it is a personal project, not a homework assignment. I am not a DBA and kindly ask for some assistance/suggestions. I will give the columns in csv format.

CO#(PK?), Model#(Also part of PK?), caseQuantity(Number), caseOnline(Date), casePartShortage(varChar),caseOut(Date) Comments(varChar), hardwareQuantity(Number), hardwareOnline(Date), hardwarePartShortage(varChar), hardwareOut(Date), Comments

I don't know if I have to make three seperate tables, or two tables, I am not really sure. I am asking for a suggestions as to how to normalize the given columns I have above into two or more tables and how to normalize. I am sorry if this seems like a trivial matter.
Reply With Quote
  #2 (permalink)  
Old 06-18-07, 06:20
r937 r937 is offline
SQL Consultant
 
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,524
perhaps you could show a few rows of this data? we don't know what those columns mean
__________________
r937.com | rudy.ca
please visit Simply SQL and buy my book
Reply With Quote
  #3 (permalink)  
Old 06-18-07, 23:25
Solidghost Solidghost is offline
Registered User
 
Join Date: Jun 2007
Posts: 4
Here is a sample row for the previously posted table.

CO#| Model# |cQTY|cO/L |cShort|Comments| hQTY| hO/L |Short|
----------------------------------------------------------------------
9n |MH200VL| 30 | 6/18/07 | 10 | | 30 |6/18/07| 15 |

/*table continued* */

cOut |hOut |hComments
--------------------------
6/29/07|6/30/07|

9n is just a combination of 9 variable characters, a mixture of text and numbers, it can be the primary key I'm assuming. If more info is needed, please let me know. I don't really know what other information I can provide.
Reply With Quote
  #4 (permalink)  
Old 06-19-07, 05:54
r937 r937 is offline
SQL Consultant
 
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,524
while i am no closer to understanding what your columns mean, it is beginning to appear that they would, indeed, be fully dependent on the primary key, so you can just leave it as one table
__________________
r937.com | rudy.ca
please visit Simply SQL and buy my book
Reply With Quote
  #5 (permalink)  
Old 06-20-07, 12:53
certus certus is offline
Registered User
 
Join Date: Dec 2003
Location: Canada
Posts: 710
Define CO#. Define Model#. Try explaining what a case is and what hardware is relative to the CO and Model and each other. This will help you understand how many tables you need.
__________________
visit: relationary
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On