HI I am still confused that whether I need to use multiple table in a single database or single table in single database??
I do have near about 30 columns for one record.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
HI I am still confused that whether I need to use multiple table in a single database or single table in single database??
I do have near about 30 columns for one record.
That’s going to be highly dependent on what kind of data you’re storing, but it’s quite common for databases to have multiple tables. Normalization is the term you want to search for and read up on.
When I say “what kind of data you’re storing” I don’t just mean in general terms like text vs. numeric data. It depends more on what specifically the table in your application represents. If you’re storing Customer data and Product data in the same table, it almost certainly should be split into two tables (or possibly more). If all of your data can be described as one type, then it might be okay to have only one table.