What is the problem of using a lot of relations in database ?

Question

1.50/5 (2 votes)

See more:

, +

Hi everybody,
I have started to design a database and every time i rethink about it, i am finding that i can use a new table instead of a field, and enhance the program ability.

but at the end i find out that there are a lot of tables with a lot of relations,so it means a lot of queries to the database, but on the other hand it can make my software what i am looking for.

what is your idea? is it wrong to use a lot of relations in a database?

thank you for you answers.

Posted 18-Sep-12 6:35am

Christ_88

Updated 18-Sep-12 6:36am

v2

Add a Solution

Comments

[no name] 18-Sep-12 13:17pm

It is not a question. You should discuss it in a suitable forum.

Christ_88 18-Sep-12 13:29pm

Could you guide me a good forum about this subject.

fjdiewornncalwe 18-Sep-12 14:14pm

Try the database forum here at CP. http://www.codeproject.com/Forums/1725/Database.aspx

Sergey Alexandrovich Kryukov 18-Sep-12 14:27pm

I don't think better forum will help more -- the problem is more fundamental, about the approach to the problem. Please see my other comments and my answer.
--SA

fjdiewornncalwe 18-Sep-12 14:36pm

I agree, sort of. I suggested the forum because this isn't really a question about coding and such, but rather a theoretical discussion topic on relational design and such. If it becomes a discussion it is better suited to the forums rather than here. Cheers.

Sergey Alexandrovich Kryukov 18-Sep-12 16:09pm

Well, then the forum you mentioned would be good to look at.
Thank you.
--SA

Christ_88 18-Sep-12 14:40pm

thank you

Sergey Alexandrovich Kryukov 18-Sep-12 14:26pm

This is not about the forum; rather, it's because your approach may be based on some misconception and because your approach to posing the problems is generally counter-productive -- please see my other comment and my answer.
--SA

Sergey Alexandrovich Kryukov 18-Sep-12 14:16pm

This is a question actually, but the approach to posing a problem is pretty much counter-productive.
--SA

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)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-09-18T08:25:00

Please see my comment to the question. Your question might be based on some your misconception or maybe the conception you do not explain.

The relationships should not really be quantified by the total number of them or something like that. And "a lot of relations" does not have to mean "a lot of queries", it you do it right. The structure of relations should be defined by the structure of actual knowledge you want to represent with a database. Perhaps you need to start approaching it all by learning about such thing as database normalization:
http://en.wikipedia.org/wiki/Database_normalization[^].

You should also understand, that one of the most important principles here is the "Don't Repeat Yourself" principle:
http://en.wikipedia.org/wiki/Don%27t_repeat_yourself[^].

And then you will be able to look for the optimization:
http://en.wikipedia.org/wiki/Database_tuning[^],
http://en.wikipedia.org/wiki/Query_optimization[^].

Good luck,

—SA