Monthly DB Records

[query_me2001]

I am new to Databases.

I want to create a data base which will have a lot of information which
is related to monthy figures. I have a number of tables that have data
entered on a monthly basis.

Should I enter the month in each of the tables or should I have a
seperate table that ties all the month records together in someway.

If anyone can point to examples or templates then this would be
appreciated.

Ta, Me

 

[Duane Hookom]

If the fields are the same, don't use multiple tables. Keep the records in a
single table with a field (or fields) that identify the month.

 

[query_me2001]

The reason I have them as seperate tables is that they are seperate
entities. The only thing that ties them together is the Month of data
entry.

I also have data tables that have a variable number of records which
has volume figures and cost per volume for that given month. Agin this
is related to a month value.

 

[Duane Hookom]

Since we don't know anything about what you are storing or where it comes
from or how it will ever be reported, you should keep it all in one table
with a field for the month.

 

[query_me2001]

OK I have a fair number of chickens. I want to be able to keep a record
of the chickes I own, how much it costs to feed them and to check the
eagg production.

So the sort of tables I have considered is

ChickenCount (This is a monthly record)
NumberChickensBeginningOf Month
ChickenBought
ChickensDied
ChickensSold

EggQuality (This is a monthly record)
NumberOfEggsLaid
NumberOfDoubleYolkers
NumberOFWhiteEggs

EggsData (This is a monthly record)
EggsUsed
EggsSold

FeedPurchased (This is a monthly record)
ProductA, Weight, Cost Per Kg for this month,
ProductB, Weight, Cost Per Kg for this month,
ProductC, Weight, Cost Per Kg for this month,

(This table will have to be slightly different at it refers to a
specific product which stores the price for a given month)

There is actually another 4 tables of specific data, each table has
about 5 entries, that is recorded on a monthly basis.

Now if I were to put all these monthly figures in a single table:

1. I thought that the items would not be categorised I would liek them
to be.
2. There may be inefficiencies storing all these values (about 25
values) in a single table.
3. I do not now how well it would expand if I wanted to change things
in the future.

I hope this is enough detail (probably as much as I know) for you to
pass comment.

TIA

 

[Duane Hookom]

I would not put your egg records in with your chicken count records. My
chicken count table (if I actually had one) would probably look more like:

tblChickenTransactions
=================
ctrCTrID
ctrTransDate
ctrQuantity
ctrTranType (bought, sold, died, ....)

I think multiple tables would suffice as long as they are not dealing with
the same entities.

I would not focus on "monthly" records since you may want more or less
granularity in the future.