• I am not sure how well I follow as there are details being lost in translation that I am not getting. It seems though you could benefit from a Calendar table with a low level of granularity, say one row for every hour all time, or for every half hour. You can add attributes that you think would be helpful such as , <off hour>. It seems your solution would be not one that could adjust very well to changes in business logic. Try practising what Sean said earlier about presenting consumable data and only what we need to understand the problem, so we dont have to sift through unneccessary detail. Just my opinion on this post. I am sure you would want someone to present a clear answer, we need you to present your problem clearly as well.

    ----------------------------------------------------