July 24, 2008 at 11:52 am
Hi,
I have design question,
Let say I have a table with 200 columns in it. And in that there is a column called Type. Out of 200 columns only first 50 are Not NULL, rest would have values based on the Type. For each row, based on Type, some column will have values rest would nulls. Lets for each Type will fill in 50 more columns.
So should have split this table, so that each Type would have its own table ?
What is pros and cons of having One Table VS Multiple Table ?
July 25, 2008 at 7:09 am
The pro to having a single table, and I see only one, is that you don't have to worry about JOIN statements in your queries. With decent indexes and appropriate TSQL code, that's a very minor issue.
The pros to having a more normalized design include, but aren't limited to:
- better performance on all your indexes
- smaller, more focused result sets, improving network performance and reducing I/O
- better data constraints to enforce your business rules.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply