• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

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.
0
Jsara
Asked:
Jsara
  • 2
1 Solution
 
JuanCarnigliaCommented:
It really depends on too many things (the data types, the model, etc).

Empty columns don't necessarily take up space. It depends on the type, and configuration of the Database.

You should examine your model, not only to better organize your information, but to optimize performance. Big tables (I mean with many columns) is never a good idea. This is why you should normalize.

Greetings
0
 
Walter RitzelSenior Software EngineerCommented:
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.
0
 
JuanCarnigliaCommented:
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.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now