April 27, 2004 at 2:07 am
Hi Gurus,
I want to know the advantage of keeping 70+ columns in a single table rather than having them in 2 tables by way of relationship. I am having a web registration page for a candidate. My team members are suggesting to keep all the columns in a single table and my argument with them is to have 2 tables.
Table 1 will consist of only those columns which are on the first screen registration (some of them are mandatory and some are not)
Table 2 will consist of other page columns which may or may not be filled by the candidate ie., he can fill up those columns if he wants to do so.
Performance wise it will be better to divide them into 2 tables rather than keeping in a single table.
I want your suggestions.
Lucky
April 27, 2004 at 2:21 am
Hi,
Sorry wrongly posted into this forum.
Lucky
April 28, 2004 at 7:18 am
It is better to keep them in one table. The overwhelming reason is Data Integrity. If you have two tables, your odds of not having them snync'd or linked on queries goes up dramatically. It will also make EVERY query from here on out at least double the work. It is a fundamentally sound database design priniciple to never split into two tables when one will suffice.
The advantages:
- queries and reports much easier to create
- data integrity
On the performance issue, I tend to disagree. Your performance will not improve by having the data in two tables. Not sure how you got there. Doesn't matter. The advantages I've listed above outweigh any slight performance hit.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply