We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

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

Jsara
Jsara asked
on
Medium Priority
335 Views
Last Modified: 2012-05-11
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.
Comment
Watch Question

Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Walter RitzelSenior Software Engineer
CERTIFIED EXPERT

Commented:
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.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.