database design and their relation ship

Question

1.00/5 (4 votes)

See more:

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

sankyn1

Add a Solution

Comments

Sergey Alexandrovich Kryukov 5-Feb-12 5:05am

How about "relation ram"? :-)
--SA

Sergey Alexandrovich Kryukov 5-Feb-12 5:07am

This is not a question. Also, please use spellchecker. Hard to read, honestly.
--SA

sankyn1 5-Feb-12 5:08am

what is that i m student so have little knwlegde what is relation ram

sankyn1 5-Feb-12 5:10am

oh sorry i m using my mobile so i write i shortcut sorry

OriginalGriff 5-Feb-12 5:12am

So? Your mobile includes vowels, doesn't it?

Amir Mahfoozi 5-Feb-12 5:12am

It is not a question.

sankyn1 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

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Wendelius · Accepted Answer · 2012-02-04T23:38:00

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[^]

Posted 4-Feb-12 23:38pm

Wendelius

OriginalGriff · Accepted Answer · 2012-02-04T23:11:00

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.