I doubt it would be noticeable, but I have never seen any performance measurements on it.
What is the actual goal? It might be easier to accomplish the desired goal with MAPI or EWS, unless the goal is "I'm the CEO and I want to see who has read the emails I send!" :) I fiddled around with this for a little while (always fun to learn new things) and getting the right message tracking report is a bit finicky. But doing it with AQS is easy "Received:Today AND Subject:'test' NOT Is:Read". But message-tracking is much more scalable than EWS if you are tracking all mailboxes and making regular search requests. One final comment: ReadTrackingEnabled only works for internally delivered email. It works differently than "Read Receipt Requested". From: [email protected] [mailto:[email protected]] On Behalf Of Joe Barrett Sent: Friday, January 17, 2014 12:11 PM To: '[email protected]' Subject: [Exchange] ReadTrackingEnabled Performance Hit? I have a customer that wants to enable ReadTrackingEnabled in their Exchange 2010 environment. Does anyone know how much of a performance hit this would be? Thanks, Joe Barrett
