Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Managing Synchronization >

Determining How Frequently to Perform Synchronization

It is recommended that you develop guidelines for how frequently your users synchronize. Make sure you recommend an appropriate interval between synchronization sessions, taking into consideration the requirements and activities of your organization. You must also consider the frequency and schedule you define for the Transaction Router.

Initially, you might recommend that users synchronize one time a day. You can then use the factors described in this topic to evaluate your synchronization traffic and determine if your synchronization schedule must be refined.

To determine how frequently to perform synchronization

• Consider the connection time.

  Frequent synchronization reduces the volume of transactions that Siebel Remote sends during a synchronization session, which reduces connection time for that session. You can evaluate the difference in connection time and cost between the following items:

  • Less frequent but longer synchronization sessions
  • More frequent but shorter sessions
• Consider the disk space requirements.

  Frequent synchronization reduces the number of transactions that accumulate between sessions, which reduces the amount of disk space required on the Siebel Server and the remote client. Evaluate the amount of disk space that is available and determine the trade off between increasing disk space and increasing synchronization frequency.

• Consider database volatility.

  Your synchronization schedule determines when changes to the server database are reflected in local databases. In an industry with high sales volatility, frequent synchronization can provide a significant advantage.

  The Transaction Router detects and routes database changes to the remote client outbox for routing during the next synchronization. The operating status of the Transaction Router on each Siebel Server affects data availability for users. In a volatile environment, it might be necessary for you to run multiple Transaction Routers for each Siebel Server. You can also stop monitoring the Transaction Router.

• Consider user productivity.

  Frequent synchronization can affect user productivity. Consider the environment in which the user operates and the convenience of completing a synchronization session.

• Consider the Siebel Server modem connections.

  The ratio of remote clients to server modem connections influences your synchronization schedule. If the ratio is high, then it might be necessary for you to assign specific synchronization times to your users.