Review my db design (please)

[Cameroncha]

Please suggest any overall db design issues that you might see visually with my db.

Is using sku as the primary key, or should i just use an autonumber field?

 

[Kevin_S]

Cameroncha -

It looks to me (and I dont know the business solution you are building the db for so please correct if misguided) like you have one master table encompassing more that one object group and then look-up tables referencing the master form. This does not follow the principles of normalization. You are going to want to look into normalization for examples on proper table layout so I would recommend searching this forum for the topic "normalization" or "nomalize database". There have been many posts that link to excellent articles posted on this subject or if your more the hardcopy type of person I recommend a book I still have in my personal library titled, "Information Modeling and Relational Databases - From Conceptual Analysis to Logical Design" by Terry Halpin.

HTH,
kevin

 

[Autoeng]

Cameroncha is normalized Kevin. The layout he shows is the results of pulling all of the data together from the many tables surrounding the query results.

Cameroncha, can you post the purpose and workings of the db so we can better comment? It appears to track a business selling sporting goods and dvd's? Using the SKU shouldn't be a problem if you feel this is relevent data and you don't mind entering it manually whereas an autonumber generates itself.

 

[Mile-O]

Cameroncha is normalized

No. There's a repeating group in the Sport table. Sporttype1,2, and 3.

 

[Rich]

There would also appear to be repeating groups for sales and producers

 

[Autoeng]

I stand doubly corrected.