Database Normalisation

[kindle]

Hi All,

This question is specific to a particular programme so i figured this is the place to post it. Sorry if its the wrong forum.

I have a question about database normalisation, as far as i am aware normalisation is conducted primarily to prevent duplication. So if you had a table with 75 fields that were unique to each record there would no need to normalise the db? ie survey results, a participant answers all 75 questions.

Cheers

K

 

[WillR]

I'd say your assumption was pretty much spot on.

 

[Andrew Fergus]

This depends on whether the list of questions is ever likely to change, or if you are conducting multiple surveys with some new and some repeating questions, or even repeating the survey with the original respondents. If the list of questions never changes and this is a one-time survey, then you may be right. However form, query and report design may prove far easier if you have the questions in their own table, i.e. 75 rows instead of 75 columns. You would then use an intermediate table with a many-to-many relationship between the respondents and questions to store the survey details and results.
Andrew

 

[kindle]

Thanks for your replies! I was just wondering what the best approach is. Have a great weekend!

K