Time series data in a relational model?

etk

Registered User.
Local time
Yesterday, 17:08
Joined
May 21, 2011
Messages
52
Hi, I have been tasked with putting together a database for 8 KPI. These KPI are measured on a weekly basis and the purpose of the database is so that it becomes easier to measure change in KPI amongst employees on a week-over-week basis.

I struggle to figure how to fit this into a relational model, but I figure something like this might do:

Three tables: KPI, Reporting_Period, Employee

Then I would make the unique identifier on the KPI table a combination of the Employee ID and the Reporting Period ID.

Does that sound rational? Is there a better way of accomplishing this?
 
Sounds to me that the database is about employees.
KPI is an attribute of employee and reporting time is an attribute of KPI.

Employee 1 to many KPI 1 to man Reporting time.

Just my thoughts.
Dale
 
Do you think it is necessary to create a table for each KPI?
 
No. Relate the table KPI to the employee table.

Dale
 

Users who are viewing this thread

Back
Top Bottom