|
Home > Archive > SQL Anywhere Mobile > November 2005 > Mobilink over WAN
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Tony Farrell 2005-11-28, 8:28 pm |
|
Hi Everyone -
We are running 7.0.3 of ASA and i am having a world of
trouble
running a client server setup over a WAN.
Very slow ODBC performance seems to be the issue, but i
am also looking at the Segments Retransmitted as a possible
issue....
BUT
i was also looking at the mobilink part of the Sybase 7
world,
and thought about something....
If i setup a local sybase on the local machine, and have it
sync
up to a master sybase system on the WAN - will this stop my
performance problems?
If there is a white paper on setup of this type of scenerio,
please advise
thanks
tony
| |
| Greg Fenton 2005-11-29, 3:24 am |
| Tony Farrell wrote:
>
> Very slow ODBC performance seems to be the issue, but i
> am also looking at the Segments Retransmitted as a possible
> issue....
>
I'm confused as to how you have the software setup right now.
Typically you have a remote machine at one end of your WAN running both
the ASA remote database and the dbmlsync client. On the other end of
your WAN you are running your consolidated database and on the same
machine (or on a machine right next to it) the ML server.
Can you describe what software you have running where? Give machine
names, what is running on each and how "far" away they are from each
other (bandwidth/speed wise, if that is possible).
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Breck Carter [TeamSybase] 2005-11-29, 9:29 am |
| I don't think he *has* MobiLink set up right now, just direct client
server via ODBC. I think his question is, "should I pursue MobiLink,
which will give me a local database that will have much faster client
server connectivity via ODBC rather than across the WAN?"
MobiLink is a big step, usually taken because the remote PC is not
always connected to the central site. MobiLink introduces latency,
which may or may not be a drawback that overshadows the increase in
local speed.
If it was me, I'd be trying to figure out why the WAN ODBC link was so
slow.
Breck
On 28 Nov 2005 19:39:15 -0800, Greg Fenton
<greg. fenton_NOSPAM_@ianyw
here.com> wrote:
>Tony Farrell wrote:
>
>I'm confused as to how you have the software setup right now.
>Typically you have a remote machine at one end of your WAN running both
>the ASA remote database and the dbmlsync client. On the other end of
>your WAN you are running your consolidated database and on the same
>machine (or on a machine right next to it) the ML server.
>
>
>Can you describe what software you have running where? Give machine
>names, what is running on each and how "far" away they are from each
>other (bandwidth/speed wise, if that is possible).
>
>greg.fenton
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Greg Fenton 2005-11-29, 1:24 pm |
| Breck Carter [TeamSybase] wrote:
>
> If it was me, I'd be trying to figure out why the WAN ODBC link was so
> slow.
>
I missed your interpretation of his original email. Yes, if this is
indeed the case then understanding why the WAN link is slow (or
unreliable) is one way to go.
If, however, you are unable to improve the WAN stability/bandwidth, then
ML is certainly the way I'd be going. It comes down to a balance of
cost/risk: moving to MobiLink will take some development effort and some
administration overhead, but if reliable access to the data/application
is of high value and the WAN stability cannot be ensured, then the
effort in moving to ML is well worth it.
If you want help in chasing down the "ODBC over WAN" issue, I suggest
posting to the general newsgroup as that is an issue around ASA not ML:
sybase.public.sqlanywhere.general
Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|
|
|
|
|