Hi all,
If I have Server A as a publisher and Server B as as subscriber, is Server A executing read of the log and performaing an update to Server B, or is Server B reading the log of Server A and updating itself? Or is it a configurable choice?
I'm just trying to get an idea of who's cpu cycles are being used for most of this work. I'm assuming disk i/o is moot because regardless of what machine is doing the thinking, the A log has to be read and the B table has to get written.
Thanks,
Jim
If I have Server A as a publisher and Server B as as subscriber, is Server A executing read of the log and performaing an update to Server B, or is Server B reading the log of Server A and updating itself? Or is it a configurable choice?
I'm just trying to get an idea of who's cpu cycles are being used for most of this work. I'm assuming disk i/o is moot because regardless of what machine is doing the thinking, the A log has to be read and the B table has to get written.
Thanks,
Jim