tables
-
I am creating a survey in asp.net to rate 46 departments from 1-5 on there quality, interpersonal skills, and timelines. Then store the data into a sql database. I am trying to figure out how I want to create the tables and I was wondering if anyone can provide any ideas. Should I create a table for each department with columns: quality, interpersonal, and timelines? If I do it this way I will have to create 46 tables which is alot. Or, should I just create one table and create columns for department, quality, interpersonal, and timelines. Any feedback would help. Thanks! jds1207
-
I am creating a survey in asp.net to rate 46 departments from 1-5 on there quality, interpersonal skills, and timelines. Then store the data into a sql database. I am trying to figure out how I want to create the tables and I was wondering if anyone can provide any ideas. Should I create a table for each department with columns: quality, interpersonal, and timelines? If I do it this way I will have to create 46 tables which is alot. Or, should I just create one table and create columns for department, quality, interpersonal, and timelines. Any feedback would help. Thanks! jds1207
I wouldn't go with creating 46 tables - as they will mostly be the same. Without more information to go on, I would look at creating this using the following structure:
Department:
ID (int autonumber PK)
Name (NVarChar(100))Rating:
ID (int autonumber PK)
Score (int)
RatingTypeID (int fk)
DepartmentID (int fk)RatingType:
ID (int autonumber PK)
Description (NVarChar(100))Then, your RatingType table would hold the types, e.g. Quality. The Department table would hold details on the department, and the Rating table would be point to the Department and to the RatingType (it would also hold the score). In this way, you get a nice flexible structure where you can add rating types in the future. I hope this helps.
Deja View - the feeling that you've seen this post before.
-
I am creating a survey in asp.net to rate 46 departments from 1-5 on there quality, interpersonal skills, and timelines. Then store the data into a sql database. I am trying to figure out how I want to create the tables and I was wondering if anyone can provide any ideas. Should I create a table for each department with columns: quality, interpersonal, and timelines? If I do it this way I will have to create 46 tables which is alot. Or, should I just create one table and create columns for department, quality, interpersonal, and timelines. Any feedback would help. Thanks! jds1207
Wow - you cross posted half the site. How annoying....
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )