Why we create masters in database?

Question

1.00/5 (3 votes)

See more:

Hello my technical frnds,

One interviewer asked me this questions that, Why we create masters in database?

I have answer this question but still I want to know yours opinion.

Thank you...

Posted 8-Oct-13 12:02pm

Shobhana.n

Updated 8-Oct-13 20:23pm

coded007

v2

Add a Solution

Comments

Mike Meinz 8-Oct-13 18:45pm

What do you mean by masters?
Are you talking about an academic degree?
Are you talking abut master-detail relationships for transaction data?
Please explain.

What is your answer?

Shobhana.n 9-Oct-13 2:01am

Suppose,If I am doing a application of Employee and their salary processing structure. to maintain the records,I will create masters in database that is Employee table (that is Employee master),Salary table(that is salary master).

Mike Meinz 9-Oct-13 7:53am

"Master" in this case refers to a table that is the primary or main table in a relation. Generally, a person, place or thing. Other tables relate to the master table. A Dependents table relates to the Employee table. An Invoice Line Item table related to the Invoice Table. An Order Line Item table relates to a Order table. The use of the terms Master and Detail originates with Electrical Accounting Machine (EAM)-based punched card applications.

The simple answer to the question "Why create Masters" is "to eliminate redundancy (duplication of data)."

1 solution

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)

coded007 · Answer 1 · 2013-10-08T20:25:00

Solution 1

We create to achieve normalizations for RDBMS

Posted 8-Oct-13 20:25pm

coded007