Best Practices for Working with Synthetic Transactions

適用於: Operations Manager 2007

As a best practice, limit the frequency of synthetic transactions.

Running synthetic transactions generates an extra load on the Exchange 2007 servers, so it is worth identifying smart limits for using synthetic transactions. You also want to ensure the accuracy of the data returned by the synthetic transaction. One way to do this is to avoid running more than one instance of the same transaction at the same time.

We recommend that you do not run synthetic transactions more frequently than once every five minutes.

If you change the timeout or frequency value for a synthetic transaction, avoid duplicate transactions by making the same change to the monitor that corresponds to the synthetic transaction you changed.