Re: Performance of ODBC

Your performance issue is not with ODBC, rather, it is your (physical)
network connection. Usiing Access front-end to connection a back end through
the Internet connection is definitely slow with currently affordable network
connection. Just compare: a typical LAN speed is 100Mbp, a very high-speed
cable connection to the Internet would be 100K - 1Mbp, 100 to 1000 times
difference. Unless you can get a network connection that fast enough and
compareable to the LAN speed (with big money), your Access front end to the
remote backend via the Internet would be alway slow and not really useful in
most cases.

You need to re-think the way to get data from remote server. For example,
using web app/service to get data; or connect via terminal services, if the
remote host provides such service; ...

"Bruce Maston" <homebrew@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E8BF6231-397F-4A4F-81BA-61773F86D668@xxxxxxxxxxxxxxxx
I apologize if this is the wrong group. I have an Access 2000 app running
at
three locations (my home, my office, and my partner's home). The database
sits on an SQL Server at a "commercial" ISP site. The machines connect to
the database via ODBC with the Jet database engine. I guess the lingo is
that Access is the front end, and the SQL server is the back end.

Over the 5 years I've used this set-up, I've always been annoyed by the
slow
response times. My database is extremely small, and it seems to me that
for
the limited information I get out of it per query and the fact that a
query
is sent to the SQL Server by somebody about once per hour, it should be
virually instantaneous.

Today I timed it as 15 seconds to make a chance in one record of one
from -1
to 0. The table has 230 records and 24 columns. Most columns are either
yes/no or have only a date in them. In other words, it took 15 seconds
for
ADO to do a
.find and then !field=no then .update.

I'm wondering if there is any way to improve this. Is there a better way
to
run my app rather than with ODBC? Would my problem improve if I had my
own
server in my office (where only the machines at home had to get data over
the
internet)? Could the problem be that the ISP's server is doing too many
other things for other customers?

I'm a hobbiest, and I'm my own IT guy. (In my "real" job, I'm a doctor.)
I
can't go to a main frame with Oracle, etc., but is there a "next level"
out
there that I should consider moving to?

Thank you for any input.


.

Relevant Pages

  • Re: remoting vs. direct sql connection
    ... I'd say that you should never expose your SQL Server directly to the ... Internet -- the security risks are simply far too great. ... Using either a web service or remoting will also somewhat help in relieving ... Remoting logically uses a connection per ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Help!! Client side database access
    ... private void StartWatch() ... Inside class checking internet connection ... > exposing your sql server on the internet and opening port 1433 on your ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: connecting to SQL Server 2000 from a VB.net app using ADO.net
    ... In terms of connectivity issues over the Internet, firewall ... TCP Ports Needed for Communication to SQL Server ... I can't create a remote connection in Enterprise Manager. ...
    (microsoft.public.sqlserver.connect)
  • Re: Connecting a PC {TO} a PC that is already connected to a network??
    ... to access the internet and share files/folders with PC1. ... Enable Internet Connection Sharing on PC1's Internet Connection: ... If there's a box labeled "Home Network Connection", ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant connect to the internet using a wireless Dlink Router
    ... >router and get its config menu, but I am not able to access the internet. ... I am not able to delete the internet gateway connection. ... Right-click and disable your local area network connection. ...
    (microsoft.public.windowsxp.network_web)