Generally speaking, records are cheap, fields are expensive.
More records and less fields.
This assumes we are aiming for normalized design and that the fields in
question can be logically broken out into other related tables. Sometimes
more fields is the proper way to go.