Moved Access DB to new server. Now opens extremely slowly.

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

Guest

I moved an Access DB to a new server. The DB was developed by long gone
others. Now when I open the database from the new server with the old server
shutdown a roughly two minute pause occurs before the database actually
opens. I've used Tools | Database Utilities | Linked Table Manager to update
references to the database table locations but still have a long pause at
startup.

The server is not heavily loaded. I've tried looking at the database in
design mode but don't see any relevant issues.

Any suggestions?
 
Once open is it slow also? I'd worry that the new server just isn't set up
properly.

I'd also check the virus checker on both the server and your PC to see if
they are scanning .MDB or .MD? files. Sometimes excluding these files from
scanning can make a big difference.

How far down the directory tree is the database? Closer to the root
sometimes makes a difference.

Also are you using mapped drives or UNCs? Mapped is faster for Access for
some reason.

I'd also make sure that users have full permissions to the folder holding
the database file.
 
Access MDB is for cripples and retards
Dont use it and dont hire anyone that does use it.

Spit on anyone that uses it.

I reccomend rewriting everything using Access Data Projects.

you should have picked up on this idea maybe 7 years ago?

-Aaron
 
Jerrel Baxter said:
I moved an Access DB to a new server. The DB was developed by long gone
others. Now when I open the database from the new server with the old server
shutdown a roughly two minute pause occurs before the database actually
opens. I've used Tools | Database Utilities | Linked Table Manager to update
references to the database table locations but still have a long pause at
startup.
Click to expand...

What OS was the old server and the new one? I suspect the old
server was NT 4.0 but I sure could be wrong.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

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
 
Jerrel,

Here is my experience: There are servers that we are logged on to and
then there are servers that we have access to.

At work we have at least two separate servers. One of them I am
actively logged on to (it is my local server housed in the same
building) and the other is one that I have access to (it is located in
another city). If the data/application is on my server response time is
fine, but if it is located on the other server, then it becomes
impossible to work in the application because of the lag time in
getting responses and loading data between the servers.

This may be the situation between your two servers.

Ron
 
yeah.. because you can't run MDB across ANY type of network with a
decent level of performance


Access Data Projects don't copy the WHOLE TABLE across the wire every
time it wants to do a table scan
 
The database is fine once it has opened. I'm fairly sure the new server is
set up properly.

I've tried totally turning off the virus scanner on the server and on the
workstation. No difference in startup speed.

The databases are in folders at the root of the drive.

I'm currently accessing the databases via UNC connections which is the way
they were accessed on the original server.

The user permissions are the same on both servers for the share name, i.e.
READ and CHANGE permissions are granted but not full access.

Jerrel Baxter
 
The old server was running Windows 2000 and is a P3 733 MHZ machine with SCSI
hard drives and 1GB RAM. The new server is running Windows 2003 and is a
Xeon 3GHZ machine with SCSI hard drives and 3GB RAM. The databases were
simply copied to the new server and the folders shared with the same access
permissions as on the old server.

Jerrel Baxter

Tony Toews said:
Jerrel Baxter said:
I moved an Access DB to a new server. The DB was developed by long gone
others. Now when I open the database from the new server with the old server
shutdown a roughly two minute pause occurs before the database actually
opens. I've used Tools | Database Utilities | Linked Table Manager to update
references to the database table locations but still have a long pause at
startup.
Click to expand...

What OS was the old server and the new one? I suspect the old
server was NT 4.0 but I sure could be wrong.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

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
Click to expand...
 
Both servers are located locally and have 1GB network adapters. The
workstations share a data switch with the servers. Not an obvious latency
problem or connection bandwidth issue :-).

Jerrel Baxter
 
What do you mean a decompile? What's the procedure for doing it? I wasn't
really aware that Access was actually compiled other than at run-time.

Jerrel Baxter

Tony Toews said:
Jerrel Baxter said:
I moved an Access DB to a new server. The DB was developed by long gone
others. Now when I open the database from the new server with the old server
shutdown a roughly two minute pause occurs before the database actually
opens. I've used Tools | Database Utilities | Linked Table Manager to update
references to the database table locations but still have a long pause at
startup.
Click to expand...

What OS was the old server and the new one? I suspect the old
server was NT 4.0 but I sure could be wrong.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

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
Click to expand...
 
Jerrel Baxter said:
What do you mean a decompile? What's the procedure for doing it? I wasn't
really aware that Access was actually compiled other than at run-time.
Click to expand...

Read the web pages.

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
 
yeah those senile dipshits always blame everything on the network

when it's _OBVIOUS_ what the problem is.

MDB isn't stable or reliable enough for a single user.. and it's
brought to it's knees by a half dozen users lol
 
dont read the webpages; find someone that knows SQL Server and rewrite
your shit.

MDB is for lepers and retards
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Tables opening slowly 4
Access 2007 Split Assets db, issue moving to new directory 0
database moved to new server now problems connecting 1
After re-linking tables to a new server, all queries don't see upd 1
re-linking Access db to new updated SQL 2005 DB 3
1 SQL Server/3 Db's to connect to 2
Moving Access databases from my computer to another person 0
Access linked databases and Windows server 2008 3

Back
Top