Re: Split DB over the internet with SQL backend?
- From: "Baz" <bazz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 23 Apr 2006 07:51:44 +0100
"Lyle Fairfield" <lylefairfield@xxxxxxx> wrote in message
news:1145742631.343833.311200@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
How fast is super fast?
LAN = 100 Mbit. VPN over the internet = depends on the bandwidth at each
end, but much, much slower than 100 Mbit.
I use an SQL db that lives on a Server in California (I am 4200 km
away), with front ends as HTA and Access ADPs on laptops and as ASP on
my web server. These are used in Canada, and from time to time in
England, France, Germany, The Czech Republic and Bulgaria.
I can recall only once that the connections have failed, and that for a
period of about 5 minutes. It's not noticeably slower than a mdb on my
own workstation.
So what? That's an entirely subjective impression, you've given no
information about the nature of the application, the amount of traffic, the
available bandwidths and so on. The original poster simply talked about
connecting client and server over the internet, he could be talking about
dialup for all you know, and if you want to give him the impression that
he's gonna get the same response over a 56k dialup as he gets over a 100
Mbit LAN then you are not helping him at all.
FWIW, I'm currently connecting to a customer's database over a VPN where the
server is sitting on the end of a leased line in London, I have a 1 Mbit
ADSL connection, and the users in China, I'm not sure what they have.
However, it IS much slower than using the app locally on their LAN. Quite
usable, but definitely slower. Sure, the app isn't designed with slow
connections in mind, but nor is the original poster's: an app which is being
converted to client/server from an old mdb app is likely to be pretty
profligate as regards it's use of the database engine.
The point about reliability is that, when it does go wrong, it is entirely
out of your hands. Jeez, it might take an hour just to get an ISP to answer
the phone!
One can get an idea of speed (and the power of ADO) by opening
http://www.ffdba.com/columns.aspchoosing some columns to show and
clicking submit, or not choosing any columns and clicking submit.
This is a very simple support db for my and relatives business account
keeping. You will find nothing complex here, and perhaps you will
realize that the whole thing has grown without much direction.
Regardless, for me in Ontario, listing the basic Table Schema for 27
tables takes less than one tenth of one second (that is the server work
takes less than one tenth of one second; the time for the html to be
sent to and displayed by my workstation is additional, but it seems to
be almost nothing). As more columns are added, more time is required,
but even with all columns selected the time is less than one-half a
second.
I have no difficulty matching or beating these results with a desktop
application using the same db.
What the hell has that got to do with it? The OP is asking about splitting
Access client and SQL Server database over the internet, and you present an
ASP application as an example. It's completely irrelevant.
.
- Follow-Ups:
- Re: Split DB over the internet with SQL backend?
- From: Lyle Fairfield
- Re: Split DB over the internet with SQL backend?
- References:
- Split DB over the internet with SQL backend?
- From: Mark 123
- Re: Split DB over the internet with SQL backend?
- From: Baz
- Re: Split DB over the internet with SQL backend?
- From: Lyle Fairfield
- Split DB over the internet with SQL backend?
- Prev by Date: Re: Job title: $300 flat for job in perl, cgi, Visual Basic/Asp.Net, whatever online project
- Next by Date: Re: Navigating from Main form to subform to sub-subform
- Previous by thread: Re: Split DB over the internet with SQL backend?
- Next by thread: Re: Split DB over the internet with SQL backend?
- Index(es):
Relevant Pages
|
