Click here to Skip to main content
11,705,610 members (45,287 online)
Rate this: bad
good
Please Sign up or sign in to vote.
See more: C# ASP.NET
plz help me to design data base and and their relation ship withother field.
My websit which i was making for my clg project it was for a institution which provide student to enroll and also a placemen and a section where a person advirtise their job and a student apply 4 job.
So plz help me to design database.and dfd and what relationship betwent and primary key and foreign key it should include plz help me
Posted 4-Feb-12 22:57pm
sankyn1456
Comments
SAKryukov at 5-Feb-12 5:05am
   
How about "relation ram"? :-)
--SA
SAKryukov at 5-Feb-12 5:07am
   
This is not a question. Also, please use spellchecker. Hard to read, honestly.
--SA
sankyn1 at 5-Feb-12 5:08am
   
what is that i m student so have little knwlegde what is relation ram
sankyn1 at 5-Feb-12 5:10am
   
oh sorry i m using my mobile so i write i shortcut sorry
OriginalGriff at 5-Feb-12 5:12am
   
So? Your mobile includes vowels, doesn't it?
Amir Mahfoozi at 5-Feb-12 5:12am
   
It is not a question.
sankyn1 at 5-Feb-12 5:22am
   
ya but any 1 of u have ans means what kind of relationship i should use how it should be design
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 2

To add to OriginalGriff's answer, few links you should go through, read and understand:
- Relational model[^]
- Entity-relationship model[^]
- Database normalization[^]
- SQL PRIMARY KEY Constraint[^]
- SQL FOREIGN KEY Constraint[^]
  Permalink  
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

Since this is your homework, I think you should do at least some of it yourself!

So, some pointers to get you thinking:

1) Think about your data. The idea is to store all the information, without repeating anything except references.
2) Each table needs a primary key. It is important that this should be unique within the table, so using a student name is probably not a good idea. Using an int (set as an identity field so that the DB handles uniqueness) or a Guid (so that you handle uniqueness is a good idea. I prefer Guids, others prefer ints - if I will have to refer to a field immediately after I insert it, then I use a Guid.
3) Look at your data, and how you are going to use it. Try it out on paper, and work out how the way you will need to use the data affects how it is best stored. Set up tables on paper, and see if it works. Try changing it, and see if that works better, or worse. Why? Is there a small change you could make to the original scheme that makes it work as well as the new one? Repeat until you are happy.
4) Remember that you can have as many tables as you want, but you don't want more than you need! The exercise in (3) should have given you a good, low number.

Think first, test second, implement last.
  Permalink  
Comments
sankyn1 at 5-Feb-12 7:23am
   
thanx a lot

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 OriginalGriff 213
1 Sergey Alexandrovich Kryukov 170
2 Inimicos 60
3 ProgramFOX 50
4 Richard MacCutchan 45
0 OriginalGriff 9,053
1 Sergey Alexandrovich Kryukov 8,347
2 CPallini 5,189
3 Maciej Los 4,726
4 Mika Wendelius 3,626


Advertise | Privacy | Mobile
Web03 | 2.8.150819.1 | Last Updated 5 Feb 2013
Copyright © CodeProject, 1999-2015
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100