I am using a SQL database to store scheduling information and to populate the ultracalendarinfo control.  In the interest of expediency it would be prudent to only retrieve appointments from the DB that conform to a specified data range.  Which works beautifully for single instance appointments.  However, for recurring appointments, the dates of the recurring appointments are not exposed, but stored in a byte bucket in the RecurringMember data element.  Thus in order to expose a recurring appointment, you must as SQL to retrieve all records whose RecurringMember data element is not null, and then parse those exposed recurring appointments to see if the dates qualify.  Is this the only viable way to handle this, or should I be using a secondary SQL table with dates for all recurring appointments?