Link to home
Start Free TrialLog in
Avatar of Jsara
Jsara

asked on

Working on normalization of our existing database - we have too many columns in a table which are empty

Working on normalization of our existing database - we have too many columns in a table which are empty?

a) Does this situation harm performance
b)Or just take space
c) What would be the fix? Is it to move such columns to other secondary tables and have 1:1 relation.
ASKER CERTIFIED SOLUTION
Avatar of JuanCarniglia
JuanCarniglia
Flag of Argentina image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Walter Ritzel
Do you know the objective of this table in your model? I mean, from a transactional perspective, a table with too many columns is not a good thing, but for example, if you use this table for reporting purposes or outbound interfaces purposes, it is not bad, because queries against your database will be simplified.
So, the tip here is: understand your model, then take a decision.
I Agree with wpcortes. A table with lots of columns, only comes in handy as a calculated table (ie a View). For instance a table you fill up once a day and drop and recreate the following day.

Greetings.