Best database design for logging time elapsed between tasks

Question

5.00/5 (1 vote)

See more:

Hi guys,

I'm designing a database for measure time elapsed between the execution of some tasks over an item.

I have two options to do this, but I don´t know which one is my best choice:

First:

Design a table with a dedicated field for each measurement parameter, to have a single row for a specific item with all the measurement parameters.

Example:

ItemId | TimeTask1 | TimeTask2 | TimeTask3 | TimeTask4 | ... | TimeTaskN

Second:

Design a table with generic fields, to have a row for each measurement parameter and identify the actual task they belong to.

Example:

ItemId | TaskId | TimeElapsed

What do you think?

Posted 11-Oct-12 19:21pm

cass3000

Add a Solution

3 solutions

Solution 1

The second way is preferred, but it all depends on how you intend to use the data.

Posted 11-Oct-12 20:15pm

Mehdi Gholam

Comments

Kuthuparakkal 12-Oct-12 17:26pm

my 5, situation(data consumption) demands the design

Solution 3

The second option is the preferred (normalized) way to do it.
As a bonus you can add a row for a task whenever it's done, your application does not need to wait for all tasks to be done before it can write it to the database.

Posted 12-Oct-12 11:01am

Jörgen Andersson

Comments

Maciej Los 12-Oct-12 17:11pm

Agree, +5!

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

damodara naidu betha · Accepted Answer · 2012-10-11T21:47:00

Hi,

I think second way is good approach. There is a flaw in first way. We can't determine
how many task will be performed on particular item. There can more than TaskN... If you design your table in first way then task count is fixed. Then We have to add a column to the table to store time taken by taskN+1..... taskN+N. So second way suits to your requirement.

Thank you