Mapped Drives and DB performance

[RickBerem]

Hi,

Some of my users start complaining about report creation
being slowed down since we changed the server of our network.

But no changes have been made in the application itself.

we were using this type of paths before
//ServerName/SharedFolder/App/Application.mdb

Now we use
U:\App\Application.mdb

I was just wondering if anyone of you guys experienced something like that or have any ideas of what is wrong

thanks for any thoughts

SG

 

[Hap007]

Dear SG,

In a perfect world, a new server should be faster, but that may not always be the case.

1) Is your new server faster than the old server?
2) Does your new server have more memory?
Hopefully yes to both 1 and 2

3) Is the new server handling the more users than the old server?
Hopefully no to question 3.

Perhaps the network card is not as fast as the old server.

Question,
Is your application set up to have a Frontend Program and a Backend database?
Is your Frontend located on the server or is it located on your local PC?

What version of Access are you using?

If you can answer these questions, I can better help you with your problem.

Thanks,
Hap



Access Developer

http://www.fcs-software.com/fcsaccessdev.html

-
Specializing in Access based Add-on Solutions for the Developer

 

[dr1256dr]

Hap has the right idea, here.

As an IT guy, I can tell you this: Sometimes when we make changes the "backbone" of the network, we re-segment, change out switches hubs or routers, etc at the same time. Also, did you change the server operating system? I don't know how big your network is, or if you have a full time Administrator, but you might want to diplomatically bounce this off him/her.

Good Luck,

Dennis

 

[RickBerem]

hi,

First things first, Thanks for your time.

I'll have to answer
1) yes
2) yes
3) no

Yes to front-end and back-end but both are on server.

Using Access 97.

SG

 

[Hap007]

Dear SG

Well, 2 thoughts here.

1) I am guessing that your new server has a later version of windows. I have heard that access 97 can run slower on newer versions of windows. I do not think that this is your problem.

2) The purpose of having frontend/backend is to allow multiple users to share the same data. The data file needs to be seen by all users. But, the frontend is the 'Program' part of the equation. If you move the front end to your local drive for all of your users, performance should be improved.

Note: an access frontend is a program. Access is different than other programs in that it has internal tables and queries that are used to run the program. Depending on how the frontend is designed, Problems can occur when users share and run the same frontend (Shared) on a network. This is very different than a 'exe' program that is read into memory. The actual access program is run from disk. You can get unpredictable record locking, and performance slow down because all activity spans the network.

So, move the Frontend to each user's Local PC harddrive and see if that works. (I am sure it will make things better)

Hope This Helps,
Hap


Access Developer

http://www.fcs-software.com/fcsaccessdev.html

-
Specializing in Access based Add-on Solutions for the Developer