Hi

It takes about 160 hours to perform the initial calendar sync, I must be doing it something wrong, there must be a better way! Any and all suggestions are greatly appreciated...

#
I am writing a server application with the responsibility to keep track of all current and future calendar appointments for all users in a company.

#
To achieve this I am relying on the EWS Managed Api 2.0 Streaming Notifications and the SyncFolderItems call, described here http://msdn.microsoft.com/en-us/library/office/ee693003%28v=exchg.80%29.aspx

#
The initial call retrieves all appointment ids in a user's calender. To determine if they are expired I must execute an additional call for each appointment to retrieve its properties, most importantly the End Date. In my case there are about 300 users with an average of 10.000 appointments in each calendar (almost all of them are expired)

#
This means that I must make about 300 0000 EWS calls to fetch fully populated appointment objects, each call takes about 200 ms which evaluates to about 160 hours to complete the initial sync operation. This is not acceptable in my environment.

thanks in advance
Matias

• Edited by Matias Krebs Friday, December 05, 2014 2:36 PM fixed incorrect wording

Hi Matias,

worry not, for the Exchange team predicted your trouble and built in a solution:

ExchangeService.LoadPropertiesForItems

Basically, all bulk operations are performed from the ExchangeService object.

Cheers,
Fred