Re: upsizing to SQL.
- From: "Kevin3NF" <KHill@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 Jun 2005 09:42:08 -0500
I believe the correct term is now Remote Desktop....
Basically you would install a new Win2K3 box with however many licenses you
need and put the Access font-end on that box, linking back to the BE tables
(you do have it split, right!?!?)....I will not even try to tell you how
many users your new TS box can support at once, or how licensing works for
Access on TS....
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnC" <JohnC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E2FD22DE-6A88-4D3E-978D-0CD41251CA3A@xxxxxxxxxxxxxxxx
> Terminal server is probably the best option. Could you advise me of the
> best
> way to approach this? Are there any web pages that you know off? Any
> issues I
> need to be aware off?
>
> I appreciate your time.
>
> John.
>
> "Rick Brandt" wrote:
>
>> 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
>>
>>
>>
.
- References:
- upsizing to SQL.
- From: JohnC
- Re: upsizing to SQL.
- From: Rick Brandt
- Re: upsizing to SQL.
- From: JohnC
- upsizing to SQL.
- Prev by Date: Re: Many to Many Relationship
- Next by Date: Re: Should I Have Only 1 Table?
- Previous by thread: Re: upsizing to SQL.
- Next by thread: How to create a Salon Database
- Index(es):
Relevant Pages
|
