Better Way To Design Database

Question

1.00/5 (1 vote)

See more:

Hi,

I have around 50 table objects.

i have common data in some of the tables like(product name, description,comment....)

ex: groceries, marbles, users, ....

all tables Name, remarks and some of the columns are common.

Future some more new tables are columns may come into addition, if we need to add table or column i need to touch my DB.

i come up with

one table with list of tables (master of tables) and column master table for in which table what are the columns

ex: table master : groceries,users..

column master: name,description,comment

table_column_Master: relation table for tablemaster and column master : PK of table master and PK of column master and one running id as PK for this table.

i have a data table to store all string values and maintaining relation with table_column_Master.

but i am thinking queries to perform any action is expensive. ex: to get userdetails queries to datatable is high (select query num = no.of columns for userdetails )

i am not getting any other design. please some one help me.

Regards,

Sekhar

Posted 5-Jun-14 0:35am

sekhar Reddy P

Add a Solution

Comments

CHill60 5-Jun-14 8:02am

SQL Server system tables will provide you with a list of tables in a database and the columns in them. If you have "common" data replicated across multiple tables then you need to learn about database normalisation[^]

Magic Wonder 5-Jun-14 9:00am

Kindly go through the concept of database normalization. It will help you to design and understand the database designing.

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)

Peter Leow · Answer 1 · 2014-06-10T19:08:00

There is no easy way to database design. Database design is more an art than science. Every database is customized to suit a particular application. It calls for hard work, meticulous, and patient. The basis of database design depends on the result and quality of requirements gathering and analysis. A well designed database will capture the workflow and business rules of an orgainization.
You will have to make many decisions in the designing process. Guidelines and principles are available in making such decisions, but they are usually about "what not to do" instead of "what to do". So, ultimately you are left pretty much alone to make the decisions.
Refer:
1. 10+pitfalls+of+database+design[^]
2. Fundamentals of Relational Database Design[^]

CHill60 · Answer 2 · 2014-06-10T07:21:00

Solution 1

Posting comment as solution as there has been no other response

SQL Server system tables will provide you with a list of tables in a database and the columns in them. If you have "common" data replicated across multiple tables then you need to learn about Database Normalization[^]

Posted 10-Jun-14 7:21am

CHill60