When trying to open a new call in dispatch or when clearing calls, there is a long delay between opening or clearing the call and the process completing.
Tracker users may notice that as the software is used more and more that the time to start and complete a task increases. This occurs because even after a dispatch call is cleared or cancelled, the system still maintains a record of that call for reporting purposes. As more and more calls are dispatched and cleared, the size of the data base will increase. If you notice this happening you can run Dispatch Reports. After a dispatch report is run, a prompt will be displayed asking whether or not the dispatch calls should be deleted. Running this report and deleting the dispatch calls will decrease the size of the database, which will help improve performance while dispatching.
Another reason that decreased performance may be noticed is when corruption occurs within the database itself. Corruption can occur for a number of reasons including exiting Tracker improperly (using Ctrl + Alt + Del to close Tracker), Tracker interacting with the database (reading or writing) to the server and the connection is lost (this is common in offices that use WiFi), hardware failure on the server (hard drive crashes), etc. If it is suspected that this is the cause of lack of performance, Tracker has a built in Repair utility to use. For the Repair utility to be run, no one can be logged into Tracker other than the person doing the repair, and that user must be using the Singler User mode. To access the Single User mode of Tracker, browse to your Tracker folder from My Computer. In the Tracker folder will be a file named zimprt.exe, double click this icon. If you try to open the Single User mode and you get an error indicating that the database is still in use, that means that Tracker is still open on a workstation. We have also seen this happen when someone is using Tracker through Remote Desktop/Terminal Services and the session did not end properly. Once you are in the Single User mode, you go to Administration > Data File Utilities > Repair. Once in Repair, choose the section of the database to repair. In this case, we would select Disaptch. *Note that before doing any type of file repair, you should back up your Tracker software beforehand.*