Re: Looking for a "Payroll" database schema

From: Palooka <>
Date: Sat, 05 Sep 2009 01:37:30 +0100
Message-ID: <fpiom.79873$RV1.43768_at_newsfe26.ams2>

On 05/09/09 00:29, joel garry wrote:
> On Sep 3, 4:20 pm, Google Poster<> wrote:
>> I am sure there are versions of this out there. It would be great to
>> educate myself on design of schemas. This can be a great textbook
>> example.
>> What I need is to put a set of payrolls in a dabatase. Think of the
>> job performed by companies like ADP or Paychex: they have lots of
>> client companies, and each client company has different payroll
>> structures and periods: some pay monthly, some pay weekly, etc. It is
>> important to record the number of hours worked, and the date the check
>> was written (payday) as opposed to when the wages were earned. A
>> realistic schema should include: regular pay, overtime pay,
>> commissions, etc.
>> I tried to design it but I simply lack the experience. All I have done
>> so far are much simpler tables. For instance, if companies pay:
>> - weekly
>> - biweekly
>> - semimonthly
>> - monthly
>> etc.
>> Should I have different tables, one for each of the pay cycles above.
>> Is it possible to structure the different cycles above in one table?
>> I guess my neurons are not wired in a rectangular-relational shape,
>> for problems like the above I immediately think of trees, graphs and
>> all kinds of non-regular structures.
>> My respects go to folks who design those complex tables.
>> Pointers and advice are most appreciated and welcome.
>> TIA,
>> -GP
> Actually, most of those companies use stuff that has come down from
> Grampa's COBOL. Then when you ask them to provide you data, they use
> some dumb-ass interface that generates an Excel-compatible output,
> different each time.
> The government rules are so complex and ever-changing, a lot of it is
> just automated manual processing.
> If you buy a packaged solution, they'll generally have some sort of
> procedural update for ever-changing data.
> Your naive homework solution will probably be better than anything you
> can buy, except for all the details which would take hundreds of man-
> years.

Hah! Like Peoplesoft you mean? No sensible design whatsoever, just 3000+ tables - one for each screen, and the backend is a gigantic slow COBOL program.

Marketing roolz.

Palooka Received on Fri Sep 04 2009 - 19:37:30 CDT

Original text of this message