SQL Anywhere Mobile - Synchronization download data scenario in 9.x versions vs. previous ones

Author

Synchronization download data scenario in 9.x versions vs. previous ones

kawoN

2006-02-14, 7:24 am

Hello,

As we see since 9.x version there is a big difference in synchronization
scenario. Especially it is visible while synchronizing large amount of data
having ASA on client side.
In previous versions we had: for each table MobiLink ran download script and
after (or even while) getting data from consolidated DB sent it to client
side.Client side user saw the progress of downloaded tables.

It seems that in version 9.x it works quite different:

1. MobiLink runs all tables download scripts, data are selected from
consolidated DB to temporary file on server side - client side user sees no
progress (it may take really long time), there is written MobilLink log at
this step
2. After running all tables download scripts MobiLink sends all data to
client side - client side user sees the progress of sending data measured in
bytes (depending on connection speed this step may take longer or shorter)
3. After receiving all data from MobiLink, dbmlsync.exe loads data to remote
DB table after table - client side user sees detailed progress of this
operation.

The problem is that especially step 1 can take really long time and client
side user has no information about liveness of the process. He may think
that the process is dead and try to kill application.

Are there any solutions for resolving this problem? Maybe there is a
possibility to run MobiLink in previous mode? Or there is a possibility to
visualize the first step?

Regards
Pawel Nowak

Reg Domaratzki \(iAnywhere Solutions\)

2006-02-16, 9:24 am

I think you might be seeing the effect of download buffering at the remote
database, which was added in v8. You can play with the DownloadBufferSize
dbmlsync extended option if you want the old behaviour back.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"

"kawoN" <bla@kawon.pl> wrote in message news:43f1d1f3@forums
-2-dub...
> Hello,
>
> As we see since 9.x version there is a big difference in synchronization
> scenario. Especially it is visible while synchronizing large amount of
data
> having ASA on client side.
> In previous versions we had: for each table MobiLink ran download script
and
> after (or even while) getting data from consolidated DB sent it to client
> side.Client side user saw the progress of downloaded tables.
>
> It seems that in version 9.x it works quite different:
>
> 1. MobiLink runs all tables download scripts, data are selected from
> consolidated DB to temporary file on server side - client side user sees
no
> progress (it may take really long time), there is written MobilLink log at
> this step
> 2. After running all tables download scripts MobiLink sends all data to
> client side - client side user sees the progress of sending data measured
in
> bytes (depending on connection speed this step may take longer or shorter)
> 3. After receiving all data from MobiLink, dbmlsync.exe loads data to
remote
> DB table after table - client side user sees detailed progress of this
> operation.
>
> The problem is that especially step 1 can take really long time and client
> side user has no information about liveness of the process. He may think
> that the process is dead and try to kill application.
>
> Are there any solutions for resolving this problem? Maybe there is a
> possibility to run MobiLink in previous mode? Or there is a possibility to
> visualize the first step?
>
> Regards
> Pawel Nowak
>

Sponsored Links