What about where large number of fields are null? One company uses one field, but theother 20 don't, so for 19 of the companies they have a field that is full of all nulls. Do that for every company, and you have each company with the same table (and a normalized table) but you have 19 fields that are all null but still taking up the space (can't fit as many records into the buffer as a result).
I could keep it as normalized, I would think, if I used the company's name as a primary key, and then joined their customized fields (from another table) to the main table, don't you think?
My boss is definately in your school of thought, but I just think we are taking a huge hit in terms of speed because of the setup. Granted, it would be a hassle and then some to change it all...but if we'd see a 2x jump in speed or something, it might be worth it...
Thus I ask, because I'm not sure when having a few extra fields start to slow things down more then doing a join.
matt
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only