Offline Sync Speed Issues and Considerations in Tour deForce

Purpose

The purpose of this technical bulletin is to inform users of Tour de Force on what could affect the offline sync process. This document outlines items to be aware of and check before performing an offline sync.

 This technical bulletin contains the following sections:

1. Connection settings
2. Account Packages
3. Sync Settings
4. Sync Filters

1. Connection Settings

There are several connection problems that could corrupt the Tour de Force Offline Database. The known connection items to look out for are:

• Users trying to sync from a Hotel internet connection on a laptop will not get the full internet connection back to the SQL server. (Example: If the internet connection at the Hotel is a 5mb connection the laptop might only connect out with 1mb or less.)
• The transfer speed that the laptop would receive from the database would only be the upload connection from the corporate office or where the SQL server is located. (Example: If the Corporate Office has a 5mb upload speed the laptop would be limited to that speed even if the connection the laptop is using has a speed of 10mb.)

• The following are ranked in order of speed and reliability:

• Internet Connections

• Satellite – 128Kbps to 1Mbps – Highly advised against when trying to perform an Offline Sync.
• DSL – 128Kbps to 3Mbps – Not extremely reliable when trying to perform an Offline Sync.
• Air Cards – 400Kbps to 1.4Mbps – These connections can work, however, it depends on the location and coverage area.
• Cable – 1Mbps – 100Mbps – Highly recommended connection when trying to perform an Offline Sync.
• Fiber – 1Mbps – 1000Gbps – This would be the best possible connection when trying to perform an Offline Sync.

• Computer Connections

• Blue Tooth – This type of connection is not a recommended option to use for an Offline Sync connection. Issues include but are not limited to; interference with signals, distance, and speed.
• Wireless – This type of connection is not recommended when running an Offline Sync. Issues include but are not limited to; distance, environment surroundings, and speed.
• Wired – This type of connection is highly recommended when running an Offline Sync. Issues to look out for; types of other devices sharing the line, be sure the device is plugged into a switch and not a hub.

2. Account Packages

Account Package selections can also slow down the Offline Sync process.

• If all Account Packages are chosen for going offline the time that it takes to complete the Sync will depend on the size of the Account Packages. It is important to only choose the Account Packages that are pertaining to certain users. (Example Account Reps would only want to take off the Accounts that pertained to that Rep. Account Managers might want to take down all Accounts that pertained to the Account Reps they were in charge of.)
  

3. Sync Settings

The Sync Settings tab has different options that users can select to speed up or slow down the Offline Sync Process.

• The important section to look at with the Sync Settings is the check boxes located under the “Include In QuickSync” section. If all items are checked the sync process takes longer to complete. It is important to only choose the information that each user needs to have taken offline. For more information on each item please refer to Tour de Force Technical Bulletin 4104.

4. Sync Filters

The Sync Filters tab allows users to choose how far back they would like to go with the following; Activities, Appointments, Documents, Email, Notes, and Tasks as well as BSI Line Item Sales. This tab also has the ability to filter down on the Accounts. This will allow Account Managers to filter directly down on a certain Account Rep or allow the Account Rep to filter on customers only in a specified territory or market.

Should the user choose to take a larger date range or not apply a filter this could cause the sync time to increase as well. Again this will all depend on the Size of the Account Packages that are coming Offline.

Version: 5.x         of   Technical Bulletin 5105