Can I splite table into multiple tables, is there any drowbacks?

Question

3.00/5 (1 vote)

See more:

hello, I am have to Create database table having aproximataly 30 fields.. is it good to get all fields in a single table..?

What I have tried:

I am going to prepare database for matrimony application. the user information is to long I am thinking that split it into multiple tables rather than a single one..
Is it good for further data manipulation operations..

Please help me..

Posted 13-Nov-16 17:50pm

Vikas Hire

Updated 14-Nov-16 17:46pm

Add a Solution

3 solutions

Solution 1

Most modern relational database engines work perfectly fine with a lot of columns per row and you generally don't need to think about it unless:

* Some columns are updated/used more often and you are better off storing those columns elsewhere so the engines have better cache/memory utilization.

Posted 13-Nov-16 18:27pm

Mehdi Gholam

Comments

Vikas Hire 14-Nov-16 6:06am

thank you.... :)

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)

Suvendu Shekhar Giri · Accepted Answer · 2016-11-13T18:41:00

Well, Normalization is what you should learn to solve this problem.
The simple rule could be all those 30 fields directly dependent on the same primary key then just keep them in the same table. However, you can keep few information in another table based on their usability but most of the people will recomend to have a single table if the above condition is true in your case.

Please refer to below links-
Database Normalization[^]
What is Normalization in SQL ? - SQLServerCentral[^]

Hope, it helps :)

Daniel Jones · Accepted Answer · 2016-11-14T17:46:00

Solution 3

To normalize the tables you will firstly need to create new tables, write SQL to insert the data into the new tables and then alter the original table.

Posted 14-Nov-16 17:46pm

Daniel Jones