Julien Cheyssial's Blog

It's all about a nice UI

<November 2008>
SuMoTuWeThFrSa
2627282930311
2345678
9101112131415
16171819202122
23242526272829
30123456


Navigation

Books I'm reading

My Articles

Subscriptions

Post Categories



Database Design: Table max column number

As I mentionned it in many of my previous posts, I'm currently working on a personal project. Since it's going to manage a lot of informations, tables of my database have a pretty big number of columns (like 30 columns)... I know what you're going to tell me : Normalize your database ! Of course I did and it's normalized, but these 30 fields really are native properties and core data of my entities.

Since the application will have a lot of users and a real need of scalability, I was wondering if 30 columns in a table is a problem or not... Does it have any consequences at the performance level ? If so, I guess I would have to normalize a bit more, but another problem appears here : over-normalization which is also a performance degradation cause... Do you guys have any advices about that ?

posted on Sunday, April 25, 2004 8:38 AM by jcheyssial





Powered by Dot Net Junkies, by Telligent Systems