I am making a game information web site and need a bit of help on how to design a table. I currently have a master table called "CharacterInfoGeneral"CREATE TABLE dbo.CharacterInfoGeneral( CharacterID int IDENTITY(0,1) NOT NULL, SectionID smallint NOT NULL, CharacterName varchar(50) NOT NULL, Gender char(1) NOT NULL DEFAULT 'U', RaceID int NOT NULL, AboutCharacter varchar(MAX) NOT NULL DEFAULT 'Sorry there is no information about this Character yet.', CONSTRAINT PK_CharacterInfoGeneral_CharacterID PRIMARY KEY CLUSTERED (CharacterID ASC), CONSTRAINT FK_CharacterInfoGeneral_SectionID FOREIGN KEY (SectionID) REFERENCES dbo.SectionInfo (SectionID), CONSTRAINT FK_CharacterInfoGeneral_RaceID FOREIGN KEY (RaceID) REFERENCES dbo.RaceInfo (RaceID) )
I now want to create a table that will house unique information for each character from specific games. There are over 150 games so far and each one has some sort of unique info. I was able to come up with two approaches for this. The first was to create a new table for each game to house the unique information and the second was to have a single table with an attribute and value colums. I am leaning tword the second way as this would mean I do not have to create new tables when ever a new game comes out. Am i on the right path with going with the attribute/value table?-- If I get used to envying others...Those things about my self I pride will slowly fade away.-Stellvia