TSQL Challenges - All Comments

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Ramireddy — Mon, 15 Mar 2010 17:45:03 GMT

Thanks Jacob, I submitted my solution..

But isn't hard-coding will limit the logic testing chances??

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Jacob Sebastian — Mon, 15 Mar 2010 15:54:37 GMT

Yes, you should hard-code it in the solution.

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Ramireddy — Mon, 15 Mar 2010 14:55:48 GMT

Jacob,

The output needs to list the schedules between the dates feb20 and feb28. Is it means, are we hard-coding these 2 dates in our solution??

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Ramireddy — Sun, 14 Mar 2010 10:40:28 GMT

ooops....understood now...thanks..

re: TSQL Challenge 25 - Appointments and Recurring Schedules

leszek_g — Sat, 13 Mar 2010 10:05:07 GMT

@Ramireddy

schedule start is Jan13th, not Feb13th

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Ramireddy — Sat, 13 Mar 2010 07:44:12 GMT

I have a doubt with the output.

Project meeting sch. start is Feb13th 10:30 and begin time 10:45.

That means, first time project meeting happened at Feb13th, 10:45

and the meeting is scheduled for every 2 days, so , next meetings will be at Feb 15,Feb 17,Feb 19,Feb 21

But in the output expected, project meeting is shown as Feb 20.

what is the reason behind this??

re: TSQL Challenge 25 - Appointments and Recurring Schedules

leszek_g — Fri, 12 Mar 2010 12:57:03 GMT

Thanks for answers

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Jacob Sebastian — Fri, 12 Mar 2010 10:19:43 GMT

dishdy is right. You can expect to have correct data as per the pattern reference.

re: TSQL Challenge 25 - Appointments and Recurring Schedules

dishdy — Fri, 12 Mar 2010 09:53:01 GMT

@leszek_g,

I think it's safe to assume that there will be no invalid data in the schedules table. You should expect only data of the type shown in the list of examples.

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Jacob Sebastian — Fri, 12 Mar 2010 08:48:07 GMT

@leszek,

"Every N" cannot come with weekends or weekdays. Weekly cannot have a weekday and Every N in the same pattern. Either it will be 'weekly every N' where you need to repeat the schedule every N week from the start date or it will be a list of one or more weekdays.

All the possible combination of patterns are given in the table under section "Pattern reference".

re: TSQL Challenge 25 - Appointments and Recurring Schedules

leszek_g — Thu, 11 Mar 2010 17:19:22 GMT

Can be for example data in the Scheduling table like these rows?

Combined patterns:

Daily 'Weekends Every N' 3

Weekly 'Mon,Wed,Fri Every N' 2

Yearly 'Last Thu Every Feb Every N',2

Not null Val without 'Every N' in Pattern:

Daily 'Weekends' 1

Pattern 'Every N' not at end:

Monthly 'Every N Third Tue' 2

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Jacob Sebastian — Thu, 11 Mar 2010 09:06:07 GMT

For 'Every N' recurring pattern, you always start from the start date of the schedule. So the first occurrence will be on the schedule start date and then it will repeat 'Every N'.

re: TSQL Challenge 25 - Appointments and Recurring Schedules

dishdy — Thu, 11 Mar 2010 08:18:12 GMT

Leonid,

I was under the impression that you make the first possible placement in the 20-feb-10 to 28-feb-10 interval and then count from there. But looking at App#3 it appears you count from the task's Sch.Start date.

Jacob,

Can you confirm this?

re: TSQL Challenge 25 - Appointments and Recurring Schedules

Leonid Koyfman — Wed, 10 Mar 2010 22:50:52 GMT

I think we need a better definition of "Every N."

What point in time should we start to count from?

Is it Sch.Start for the TaskName?

re: TSQL Challenge 25 - Appointments and Recurring Schedules

dishdy — Wed, 10 Mar 2010 16:41:57 GMT

@leszek_g,

You are free to hard code those dates any way you like. You can even hard code information derived from those two dates.

If you use a CTE approach you might want throw these two dates into a table with a single row and possibly any other information you find useful.

This way you have to do the hard-coding only once.