Improve Synchronization Performance by Reducing the Log Record Size

Improve synchronization performance and free Unwired Server resources by deleting log records from Unwired Server and the client when no longer needed.

A large log record table can negatively impact client synchronization performance. Each package contains a single log record table that consists of:

Unwired Server operation replay logs – downloaded to the device when the application synchronizes. Unwired Server generates a log record if the operation replay fails, or succeeds but results in a warning.
Client logs generated by the application – uploaded from the device to Unwired Server for audit and logging purposes.

If the application and Unwired Server do not delete these log records, the log record table continues to grow.

Unrestricted growth of the log record table eventually affects synchronization performance. You can view client log records from Sybase Control Center; however, this displays only active log records (that is, those that have not been logically deleted). A logically deleted log record is marked for deletion but retained until the application downloads the delete record and deletes the copy from the device. Once Unwired Server confirms that the application has downloaded the delete, the inactive log record can be physically removed from Unwired Server.

Determining the Log Record Size
Use Sybase® Central to query the database of a given Unwired Server to determine the size of the log record.
Reducing the Log Record Size
Use Sybase Control Center to delete log record entries by setting a date range window.

Parent topic: Troubleshoot Synchronization