Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
opi
Starting Member
29 Posts |
 Posted - 2008-03-10 : 18:21:07
|
Hi,Hope someone can help me with this question, actually I'm looking for some verification.Currently I'm creating a Resume web application. I have a Resume with different skill types, hardware knowledge, programming knowledge etc. I created the following design, think this should be right, but if it's net, please let me know... Skilltype can be Hardware, Networking, Programming..Skill can be (for hardware) windows mac, with the skillType id for hardwareResumeSkills is a link between the resume and the skill.And it should be possible to set multiple ResumeSkills / Resume.Is my design ok or does it need tweaking ?Thanx in advance |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-03-10 : 18:28:14
|
| you should have foreign assigned to primary key as well in Data architect. |
 |
|
|
opi
Starting Member
29 Posts |
Posted - 2008-03-10 : 18:40:51
|
| Sorry can you be a bit more specific ? |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-03-10 : 18:52:06
|
| Like this:ALTER TABLE ResumeSkillsADD CONSTRAINT FK_SALES_Resume FOREIGN KEY (SkillId)REFERENCES Skills(SkillId)andALTER TABLE ResumeSkillsADD CONSTRAINT FK_SALES_Resume2 FOREIGN KEY (ResumeId)REFERENCES Skills(ResumeId) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-10 : 19:23:44
|
| sodeep, these are covered in his ERD already. Just look at the connectors.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
Lamprey
Master Smack Fu Yak Hacker
4614 Posts |
Posted - 2008-03-10 : 19:31:43
|
| On your ResumeSkills table, there is no need for a surrogate key (ResumeSkillID). The combination of ResumeID and SkillID are enough. So, I'd make ResumeID, SkillID your Primary Key (in that order) on ResumeSkills table and drop the ResumeSkillID surrogate.--- Added comments below this line.Do you have some more examples of Skills? Something is not sitting right with me on the Skills-SkillType relation.The more I think about it it seems that a Skill is a combination of potitially different things: Hardware, OS, Programming Lnaguage, Programing Language or Platform Version (SQL 6.5, 7.0, 2000,; .Net 1.0, 2.0, etc), and probably others. Sorry for rambling, I was just sorta putting down some thoughts. Hopefully, it helped.. :) |
|
|
|
opi
Starting Member
29 Posts |
Posted - 2008-03-11 : 02:42:00
|
| So the design is ok ?Lamprey,The examples I had in my mind are the ones you have I think.I didn't want to create a table for every different skills, that's why I did it this way...This way the user can have all sorts of different skills on his resume |
|
|
|
|
|
|
|
|
Many to many SQL deisgn