I have completed some prototpe testing of a SQL Server-based app using just a handful of appointments and that went well. The appointments are objects based on an extended Appointment class. I am using DataSets to store the retrieved data but saving any changes back to the database at the time they are made. (Calling stored procedures, not the DataAdapter's Update method.) I have encountered no speed issues whatsoever. Performance is definitely acceptable.
I am now gearing up for a full blown test with 'real data' imported from multiple Outlook calendars. I anticipate the biggest performance-related factors to be:
1) The date range for appointments retrieved from the database into the DataSet
2) The number of calendars ('resources') you wish to include for that date range
3) The number of Dates to Add to the TimetableSettings at any one time
I am looking forward to playing around with these parameters to find optimum settings. From prototype testing, I know acceptable performance can be achieved, I just need to know how far I can push the envelope.
As a side note, I am much impressed with Meppy's plan for implementing external data binding for Calendar items in the next release. From playing around with Planner .NET I can see this would involve an incredible amount of work. I remain 'cautiously optimistic'.