Performance issue with San Server

[angela.gard]

We recently implemented a san solution for our network.
Our Access database have seen a major degradation. All
sizes of databases some <100 records and some over>10000
and they all are choking. Seems to only be on the SAN
server, servers outside of that environment are not
having the issue with the same database. We use fe and
backends, batch files to launch the msaccess executable
open the database and run the mdw...

Any help would be great!

 

[Tony Toews]

We recently implemented a san solution for our network.
Our Access database have seen a major degradation. All
sizes of databases some <100 records and some over>10000
and they all are choking. Seems to only be on the SAN
server, servers outside of that environment are not
having the issue with the same database. We use fe and
backends, batch files to launch the msaccess executable
open the database and run the mdw...

Is the OS running on the San Server Windows Server or other? If other
then I'm not sure there's a lot we can do to help you.

I'll post my standard performance blurb but I doubt it'll help.

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