Anyone have any experience connecting to an instance of SQLServer on a
server that is rather distant from your local office? (EX: Office in
Chicago, Server in Atlanta)

On Thu, 4 Mar 2010 19:10:37 -0500, "David C. Holley" <David.C.Holley>
wrote:

Yes. Worked fine. What's your challenge?

-Tom.
Microsoft Access MVP


>Anyone have any experience connecting to an instance of SQLServer on a
>server that is rather distant from your local office? (EX: Office in
>Chicago, Server in Atlanta)
>

Lack of experience with it and on a very-high profile project. I'm going
into it blind as a bat.

"Tom van Stiphout" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> On Thu, 4 Mar 2010 19:10:37 -0500, "David C. Holley" <David.C.Holley>
> wrote:
>
> Yes. Worked fine. What's your challenge?
>
> -Tom.
> Microsoft Access MVP
>
>
>>Anyone have any experience connecting to an instance of SQLServer on a
>>server that is rather distant from your local office? (EX: Office in
>>Chicago, Server in Atlanta)
>>

Yes, slow.

Never had a user that actually liked the experience.

Never bad enough to make management think that
the users had a problem.

But bad enough to make management think that management
had a problem if management had to use the application.

And that was using a fairly well designed application.

Depends a lot on the network infrastructure, not so much
at all on how far physically.

Latency is more important than through-put. Or at least,
you can fix through-put problems just by fixing up your
design.

Exaggerates all of the problems of ODBC-linked table design.
-- complex multi-table joins will be candidates for re-design
as views.

(david)



"David C. Holley" <David.C.Holley> wrote in message
news:u$7TJh$(E-Mail Removed)...
> Anyone have any experience connecting to an instance of SQLServer on a
> server that is rather distant from your local office? (EX: Office in
> Chicago, Server in Atlanta)
>