Executing Access from file share

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an mdb that links to a SQL Server Table. I run a query on this table
on my local machine and the performance is very resonsable.

When I place the file on a server, I have access to it via a file share.
Opening the mdb is not am issue. But, when I run the same query, the
performance is unbelievably slow. WHat causes the significant slow down when
running the app from a file share on a different computer (faster)?

I'm thinking virus scan, or something like that. Any thoughts?
 
While the database may be on the server, execution is actually happening on
your workstation. Information is transferred back and forth between your
workstation during this.
 
DOug,

Thanks. I expected as much. So, I know I'm opening a copy on my machine
when I click on it from a file share (on the server). When I run the query,
I know that I'm updating the table resident in memory on my machine. But, is
the performance issue bacause I'm also updating the copy on the file share
(server)..record by record? Or is this done, after the query and when I
save. Seems to me that the performance problem would be related to going
back and forth, but I was trying to understand exactly what is happening.
Can you elaborate?

Thanks again.
 
jjflash said:
DOug,

Thanks. I expected as much. So, I know I'm opening a copy on my machine
when I click on it from a file share (on the server). When I run the query,
I know that I'm updating the table resident in memory on my machine. But, is
the performance issue bacause I'm also updating the copy on the file share
(server)..record by record? Or is this done, after the query and when I
save. Seems to me that the performance problem would be related to going
back and forth, but I was trying to understand exactly what is happening.
Can you elaborate?
Click to expand...

Think of it this way. The server is nothing more than a hard drive on the
end of a really long cable. The *exact same* i/o that would happen on a
local disk is what occurs over the LAN wire.

BTW when you run an update query you are NOT updating a "table in memory".
You are updating the file on the server.
 
Thanks Rick. Your response is clear. I understand the mdb is getting
updated on the server. I assume the update query is exuected on my local
machine (ODBC connection to another DB on #2 server) and the records are then
sent back to my local (#0 machine and the stored in the mdb on the server
(server #1).

The additional time for this operation is really just the fact that we have
to write the records to the server (#1 wher the mdb resides) versus just
haveing the mdb on my local (#0) machine and writing the mdb there.

The performance in running the mdb from the file share is terrible versus on
the local machine.

So, I trying to get at why. The LAN speeds are the same. I looked at the
LAN speed to/from the Server (#1 where mdb resies) to local machine and it's
performaing fine ( I tried copies to and from and measured). SO, I'm
assuming the the poor performance is do to writing the mdb on the file sahre.
I mean it's terrible. SO slow that we have to kill the update query. So
I'm trying to understand why the performance hit if it's not LAN speed. I've
read about TCPIP loopback performance issues if you use a "share" on the
local machine. I was wondering if tehre are similar issues using a share
from a remote server in executing the MDB> Or a difference in teh way the
mdb file is written in the context of "over the LAN".

I appreciate the feedback.

Thanks Again
 
Back
Top