"Shabam" <chalupa@yomama-nospam.com> wrote in message
news:WfGdnY8zBunyxFzcRVn-3g@adelphia.com...
> I'm having a calendar feature developed whereby users can add recurring
> events. These recurring events can have start and end dates, meaning they
> will recur only within a date range. For instance, user A creates an
event
> that recurs every Tuesday, from 1/1/05 - 3/2/06.
>
> The developer has decided that it would be good to have another table that
> stores each individual recurring event in a separate record. His logic is
> that this will help with the display of calendar months. His logic is, if
> the application has to dynamically iterate through every event record in
the
> database and logically map out which days have recurrence, that it would
not
> be good for performance.
>
> My take though, is that if one recurring event can literally add in 10,000
> records, then that's even worse.
>
> What are your thoughts on the proper way to implement this?
>
>
>

"Shabam" <chalupa@yomama-nospam.com> wrote in message news:WfGdnY8zBunyxFzcRVn-3g@adelphia.com...
> I'm having a calendar feature developed whereby users can add recurring
> events. These recurring events can have start and end dates, meaning they
> will recur only within a date range. For instance, user A creates an event
> that recurs every Tuesday, from 1/1/05 - 3/2/06.
>
> The developer has decided that it would be good to have another table that
> stores each individual recurring event in a separate record. His logic is
> that this will help with the display of calendar months. His logic is, if
> the application has to dynamically iterate through every event record in the
> database and logically map out which days have recurrence, that it would not
> be good for performance.
>
> My take though, is that if one recurring event can literally add in 10,000
> records, then that's even worse.
>
> What are your thoughts on the proper way to implement this?
>
>
>

"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in message
news:e17lkG24EHA.2592@TK2MSFTNGP09.phx.gbl...
> sp_msforeachdb 'EXEC sp_helpfile'
>
> Note that sp_msforeachdb is not documented, not supported etc. Also, if you don't like the result
> structure, you can easily change that by taking the source for from sp_helpfile and write your own
> version that presents the information in a way that you like it.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "Shabam" <chalupa@yomama-nospam.com> wrote in message news:WfGdnY8zBunyxFzcRVn-3g@adelphia.com...
>> I'm having a calendar feature developed whereby users can add recurring
>> events. These recurring events can have start and end dates, meaning they
>> will recur only within a date range. For instance, user A creates an event
>> that recurs every Tuesday, from 1/1/05 - 3/2/06.
>>
>> The developer has decided that it would be good to have another table that
>> stores each individual recurring event in a separate record. His logic is
>> that this will help with the display of calendar months. His logic is, if
>> the application has to dynamically iterate through every event record in the
>> database and logically map out which days have recurrence, that it would not
>> be good for performance.
>>
>> My take though, is that if one recurring event can literally add in 10,000
>> records, then that's even worse.
>>
>> What are your thoughts on the proper way to implement this?
>>
>>
>>
>
>