File access performance from remote Share

Architecture: 2 Windows 2003 Enterprise Servers, one at location A and the
other a 1000 miles away at location B.
Scenario: I have a fairly large .txt data file at one site (A) that is used
as input to an .exe program that executed at site B.
Question: Should I first copy the .txt file to site B then process it? Does
Windows Server do this transparently anyway? Should I even worry about this?
Thanks, puzzler8

"Puzzler8" <(E-Mail Removed)> wrote in message...
> Architecture: 2 Windows 2003 Enterprise Servers, one at location A and the
> other a 1000 miles away at location B.
> Scenario: I have a fairly large .txt data file at one site (A) that is
> used
> as input to an .exe program that executed at site B.
> Question: Should I first copy the .txt file to site B then process it?
> Does
> Windows Server do this transparently anyway? Should I even worry about
> this?
> Thanks, puzzler8

Performance would obviously be better if the .txt file was read locally and
has a better guarantee of successful execution than reading over a
potentially unreliable WAN link. This outweighs the cost of copying the
file across the WAN, IMHO.

--
Todd J Heron, MVP Windows Server - Networking
MCSE - Windows Server 2003/2000/NT; CCA