| jmorris 2006-03-16, 7:28 am |
| Using Adaptive Server Anywhere static C++, UltraLite Code Generator
Version 9.0.2.3131
on Palm 5.x platforms, T3, TX and Treo 650 via HotSync
Currently we are essentially using the snapshot methodology to download
table. The download_delete_curs
or is used to truncate the tables then
all the values are downloaded. As has been discussed in other messages
this results in an approximate doubling of the database size.
We would like to avoid this doubling.
>From ealier messages use of StopSynchronizationD
elete on the client
seems to help to some degree however this seems to require that a
change date or flag is used to condition the deletes on the pre-HotSync
event (Be nice if the Ultralite flag were queryable). It also has the
undesirable side effect of leaving the database in a bad state on sync
failure.
We have tried to think outside the box and had some ideas.
1) Can a commit on the client be done after the delete stage so as to
allow reuse of the space, perhaps in the end_download_deletes
event?
2) Will setting the checkpoint_store parameter in the client reduce the
database size after sync?
3) Can synchronization be spit into discrete upload-only, delete and
download syncs each with their own commits but occuring in one HotSync?
Are there any other possible approaches to limiting the doubling of
space?
If we were to convert to incremental downloads I assume the doubling
effect is minimized, correct?
Thanks
|