Re: upsizing to SQL.
- From: "Rick Brandt" <rickbrandt2@xxxxxxxxxxx>
- Date: Tue, 28 Jun 2005 13:13:30 GMT
JohnC wrote:
> Until recently my Access Project was LAN based & ran very well. Now
> the test period is over & the system has been accepted it is
> necessary to run the database over a WAN. There is a dramatic speed
> difference so I'm looking for solutions. I have optimized the project
> & the WAN connection is good but it is still running slowly.
> Apparently my options (without completely re-designing) are either
> some kind of Thin Client server or SQL. Could anybody indicate which
> solution is best & maybe offer some kind of starters checklist! I've
> been using Access for a year but I have no knowledge of SQL at all.
>
> Thank you in advance,
>
> Regards John.
SQL Server only solves the problem of the unreliable WAN connection
corrupting your data (as it would almost certainly do with an MDB back end).
It will not make performance any better. Your performance problems are
caused by how long it takes to pull the data over the WAN connection. Using
SQL Server doesn't magically make that problem go away.
Didn't the "test period" take into account the fact that the fastest WAN is
still 10 to 100 times slower than a pretty crappy LAN and thousands of times
slower than a really good one?
You should either create a web-based front end for the data or look into a
remote (thin client) solution like Terminal Server.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
.
- Follow-Ups:
- Re: upsizing to SQL.
- From: JohnC
- Re: upsizing to SQL.
- From: Kevin3NF
- Re: upsizing to SQL.
- References:
- upsizing to SQL.
- From: JohnC
- upsizing to SQL.
- Prev by Date: How to create a Salon Database
- Next by Date: Re: upsizing to SQL.
- Previous by thread: upsizing to SQL.
- Next by thread: Re: upsizing to SQL.
- Index(es):
Relevant Pages
|