one ore many sql tables

Question

Hi,
I build an application for a factory. Each workers has his/her transactions. A few hundred workers, a few hundred transact/per worker/year.
Which is better:
1.  to create programtically a 'personal transaction' table (in sql of course), for each wokers when he/her joins the factory and drop the table when he/she quits.
or
2. build and feed a single huge table with all transactions of all the wokers?



 
 

Answer 1

Ok

Answer 2

A basic idea I have.
In the between time I've found this: http://www.sql-server-performance.com/tips/database_design_p1.aspx
This explains me the issue clearly and deeply. Thanx anyway.

Answer 3

First , have you ever basic idea about relational data base conception or not?