too many fields in table?

[emrys404]

Hello, i am creating a database that has a table with close to 35 fields. I was wondering, is this too much? Should i break it down? There is no real logical way to break it down other wise i would have already. I am just wondering if it is bad practice to have so many fields in one table.

Sorry for the n00b question
-emrys

[LordShryku]

Not really bad practice if you can't break it down.......but there's always a way to break it down. And unless you are always going to use all of those fields, you should look at splitting it out to seperate tables.

[Danicek]

If it is not logical to split it, you should mainly focus on your future use of this table.
Many collumns mean larger rows and therefor less rows on datapages. Such tables could bring several problems.
However you should ask yourself like this (if all or most answers are yes, let it be, if answers are no, split it):
- select statements mainly need all or most collumns
- more then 1 collumn will be very large (text, image, large varchar)
- there will be no same values in many rows in one collumn