We have a table TIMED_EVENTS_QUEUE, that stores events and times (like a job schedule). Some of these events will be repeating, (e.g. every day, or just ran 10 times). At the moment this is stored in one table, eg.
TIMED_EVENTS_QUEUE:
EVENT_ID
USER_ID
EVENT_DESC
EVENT_TIME
REPEAT_ON
REPEAT_INTERVAL
NEXT_EVENT_TIME
STATUS
Now a colleague wants to change this into two tables for performance purposes, e.g.
TIMED_EVENTS_QUEUE: REPEATING_EVENTS:
EVENT_ID EVENT_ID
USER_ID USER_ID
EVENT_DESC INITIAL_EVENT_TIME
EVENT_TIME NEXT_EVENT_TIME
REPEAT_ON INTERVAL
STATUS a 1-0 relationship
My query is, if it is a 1-0 relationship and these two tables are always joined when quering or updating, the extra table will be futile, more maintenance (within the application), and use more space. Am I correct, or does anyone see the need for this extra table? Thanks.