Folks,
I currently have a employee management database that stores employee hours. It is spread across two tables currently, timecard and timecarddetail. One-to-many relationship. Timecard detail can conceivably contain records-to-limitation number of records for each Timecard. Unfortunately, over the years, the database has grown dramatically, around 300000 records in the Timecarddetail table alone.
Now, whenever I query the data to obtain historical versus current performance, the queries are taking a heck of a long time.
My question is, should I redesign the timecard structure to be based upon inidividual employees (ie. store timecard data in tables for each employee), or continue with the same structure and move towards an enterprise level DBMS? (The current database is quite a bit more involved than straight time management, but the timecard data is one of the bigger performance issues).
Thanks in advance,
p.
I currently have a employee management database that stores employee hours. It is spread across two tables currently, timecard and timecarddetail. One-to-many relationship. Timecard detail can conceivably contain records-to-limitation number of records for each Timecard. Unfortunately, over the years, the database has grown dramatically, around 300000 records in the Timecarddetail table alone.
Now, whenever I query the data to obtain historical versus current performance, the queries are taking a heck of a long time.
My question is, should I redesign the timecard structure to be based upon inidividual employees (ie. store timecard data in tables for each employee), or continue with the same structure and move towards an enterprise level DBMS? (The current database is quite a bit more involved than straight time management, but the timecard data is one of the bigger performance issues).
Thanks in advance,
p.