Sluggishness in MDB file after database migration

[Shohoku79]

Hello:

We have an access database in the office that was sitting on server 1 and
being shared by at most 5-7 users at the same time over a domain. Server 1 is
old and we are looking to slowly retire it so we moved everything to a newer
more powerful server 2 (including this database).

However, it seems that whenever I shutdown server 1 in order to see if there
are any users still accessing server 1 materials, I noticed this file (now
resides on server 2) experiences very slow, sluggish responses when opening a
table inside the database. The table will eventually open, but at about 1/2
to 1/4 of the speed if server 1 was kept on.

Logical responses is to go into the databae codes and inspect to see if
there are anything within this database that is still trying to access server
1 resources . There was one instance where page setup with the forms/tables
seem to be using a Specific Printer (connected using server 1 properties) and
that has since then been changed to Default Printer (and runs using server 2
properties). However, I can't seem to figure out what else would be there to
cause this, and whenever a user comes to report slowness in this database, I
had to go turn on server 1 just for the database to run normally even though
the resource is on server 2.

Any suggestions on where else I might be able to look to?

Thank you

 

[david]

Have a look at Tony's performance FAQ:

http://www.granite.ab.ca/access/performancefaq.htm

All of those ideas are more critical with newer software,
which tends to run slower.

SMB signing is particularly likely if you are changing to a new server, but
if you haven't done the other things, you might be able to pick up the
difference even without server tuning.

(david)

 

[Shohoku79]

Ok, I re-checked the database again when I had some time. And apparently the
database was still using a Linked Table where the link points to a resource
that was back on server1. After correcting that to point to link to the
correct resource on server2, everything worked fine.

Thank you for your tips.

 

[Tony Toews [MVP]]

Ok, I re-checked the database again when I had some time. And apparently the
database was still using a Linked Table where the link points to a resource
that was back on server1. After correcting that to point to link to the
correct resource on server2, everything worked fine.

Yup, that's been reported before as a problem.

FWIW I have code that double checks all the linked tables in my
database and ensures they are all pointing to the same BE MDB.
Although that's more for bizarre cases where relinking logic only gets
half way through and dies for some strange reason.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/