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?