Re: ADO over WAN

Thanks for your input.
We are using server-side cursors on the bigger datasets (actually, the
dataset is over 10,000 records), but even the smaller queries returning less
than 10 records have the same performance problem. Just returning a
recordcount takes forever. Any ideas?
Morten

"Arnie" <NoOne@xxxxxxxx> wrote in message
news:45b51c4f@xxxxxxxxxxxxxxxxxxxxxxxxx
"Morten" <na@xxxxxx> wrote in message
news:45b4faa5$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Has anyone successfully run a client/server application connected to a
SQL Server over WAN with good performance?

Yes.

Over LAN environment our query takes
4 seconds, but over WAN it takes about 3 minutes. Of course, this could
be a physical limitation, but I am curious if it's even possible to make
this work.

Morten

I't really a function of much data is being returned to the client. If
you're using a table component, all of the table data will be shipped to
the client. If you're using a query component with a client-side cursor,
the entire result set will be shipped to the client.

I do some of my development at home over a VPN. While it's noticeably
slower, it works pretty well. However, it's not advisable to "SELECT *
FROM MyTable" when MyTable has 20,000,000 rows ;-)

- Arnie



.

Relevant Pages

  • Re: ADO over WAN
    ... We are using server-side cursors on the bigger datasets (actually, ... I't really a function of much data is being returned to the client. ... If you're using a query component with a ...
    (borland.public.delphi.database.ado)
  • Re: ADO over WAN
    ... We are using server-side cursors on the bigger datasets (actually, ... Brian asked a pertinent question below. ... used in both the LAN and WAN scenario? ...
    (borland.public.delphi.database.ado)