Inconsistent behavior in transaction logs.
I just asked a related question in the development forum (http://social.technet.microsoft.com/Forums/en-us/exchangesvrdevelopment/thread/11c21e9c-42f3-41d0-babe-257b2ec11c85), but here's an angle on the same problem that's a bit more admin-centric, so I'll post it here: As I mentioned in the other question, I use Exchange Web Services to do bidirectional synchronization between Exchange and an external system. And from looking at the transaction logs (using ExMon, and just by counting the .log files in Explorer), the amount of logs generated per synchronization varies hugely, even when only read operations are performed (if there is nothing to synchronize, the service just checks that everything is up to date). In one iteration, my EWS calls caused (or coincided with) 20MB of log files, and in another, ExMon reported a mere 9KB of log being written. What's even more baffling is that I also tested when items *were* being synchronized (by adding an appointment in each system, which were then synchronized to the other side), and here *nothing* was written in the log file. The files didn't even have their "last modified" timestamp updated. Are there circumstances where Exchange bypasses the transaction logs? Or can anyone explain what is going on?
March 24th, 2011 5:45am

Hi Maybe you can post it to this forum. http://social.msdn.microsoft.com/Forums/en-us/categories/Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2011 10:12am

I'm sorry, I don't see how it would be any more relevant on the *general* MSDN forums, which don't even have a subforum for Exchange or Exchange web services.
March 25th, 2011 12:52pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics