Help With Normalization

[artisticre]

I have a database
CREATE TABLE Wine (
WineID tinyint(4) NOT NULL auto_increment,
labelD tinyint(4) NOT NULL default '0',
varietalID tinyint(4) NOT NULL default '0',
typeID tinyint(4) NOT NULL default '0',
regionID tinyint(4) NOT NULL default '0',
countryID tinyint(4) NOT NULL default '0',
ratingID tinyint(4) NOT NULL default '0',
availabilityID tinyint(4) NOT NULL default '0',
caspriceID tinyint(4) NOT NULL default '0',
bottlepriceID tinyint(4) NOT NULL default '0',
PRIMARY KEY (WineID)
) TYPE=MyISAM;

This holds the ID's for the subsequent tables. LabelID is a table called Label, varietalID is a table called Varietal. I am really new to databases and trying to learn this on my own. Is this the correct way to cut down on redundancy and if not could someone show me the correct way?

Thanks in advance

[ultraslacker]

WineID throught CountryID could refer to entities as I see possibilities for more information in the relation than contained in the wine table, so your schema makes sense up to that point. In other words, you would be adding redundancy if you were to store a labels name and address instead of labelID.

Availability, casprice, bottleprice, and perhaps rating strike me more as attributes of wine without further information required or expected - from a database design point of view, this isn't redundancy. Rating would be best left as ratingID if you need to embellish upon what the rating means in a separate table.

[artisticre]

I don't follow. Can you show me an example?

thanks

[ultraslacker]

Here's an normalization tutorial - datamodel.org

[ultraslacker]

This one may be better - http://www.sims.berkeley.edu/courses/is202/f98/Lecture12/sld001.htm