Efficient Table Design

[capik79]

Hi Guys,

I have a 35 records to be store. So which design should I use?

1. Create SIngle table and store all 35 records inside the table

2. Create Parent Tbl and child table to store the 35 record.

Which one more efficient and faster when we do query (display, insert & Update)

Thx in advance

Regards,
Shaffiq

[JaredJBlackburn]

Generally speaking, queries run against a single table execute faster than
queries run against multiple tables that have to be joined together. If all
the data is in the same place, there's simply less work to be done. This is
why you'll hear of some databases being 'denormalized for performance reasons.'
They are removing some of the normalized, multi-table design in order to gain
faster query execution.

That said, with small amounts of data, the difference will be a small one,
and, while performance is important, there are many other factors to consider
in database design. Most designs will go for a more normalized approach that
uses multiple tables - sacrificing performance to gain data integrity, ease of
maintenance and a more robust system.

[elDonrico]

shaffiq,

you are only going to have 35 records in this database? are you sure that is
all you will ever have?... a good "normalized" database and good SQL queries
can actually make your queries run faster than a single table db. but, if you
are only going to have 35 records, neither method should be slow, and depending
on the type of information you are talking about, (and your experience in
coding) it may be an easier and quicker just to leave it in one table.