Dao.database opendatabase vista performance

[Greg Keane]

I've got an application not written by me that is performing incredibly
poorly in vista in access 2007. We've isolated it to the running
opendatabase on a dao.database object. If 20 machines try to open the
database at the same time in vista the last machine takes up to 30 seconds.
In xp it is instantaneous for all machines.

Why the huge difference?

I've disabled autotuning on the nic and haven't seen a difference.
I've suggested to them to use persistent database connections, but they just
want to blame Vista.

 

[Allen Browne]

Could be several things.

Presumably you have split the database, so each user has a separate instance
of the front end.

Hopefully you have applied Service Pack 1 for Office 2007. You might also
investiage whether any of the hotfixes help, e.g.:
http://support.microsoft.com/kb/960307
http://support.microsoft.com/kb/957690
List of updates and hotfixes for A2007:
http://allenbrowne.com/Access2007.html

Keeping the path short makes a difference.

Other things like turning off subdatatsheets can help too. Tony Towes has a
list of suggestions here:
http://www.granite.ab.ca/access/performancefaq.htm

 

[Albert D. Kallal]

I've got an application not written by me that is performing incredibly
poorly in vista in access 2007. We've isolated it to the running
opendatabase on a dao.database object. If 20 machines try to open the
database at the same time in vista the last machine takes up to 30
seconds.
In xp it is instantaneous for all machines.

Why the huge difference?

I've disabled autotuning on the nic and haven't seen a difference.
I've suggested to them to use persistent database connections, but they
just
want to blame Vista.

Likely all kind of extra security and authentication is going on. and, some
cases it might be somewhat more aggressive in trying to lock the file
exclusive to INCREASE performance. if access can't get exclusive open to the
file, then it will fall back to multi-user mode.

If you don't implement that persistent connection, then a billion gazillion
network and grabbing things occur.

Try the persistent connection, as I seen this problem even occur on windows
xp boxes (and, furthermore I had a BIG BOAST in performance as a result of
doing this).

Really, why slow your application down to the speed of windows networking
that trying to do a BILLION GAZILLION things? force a persistent connection,
and you not be waiting for windows networking anymore because you are
forcing your connection to remain open an all of those huge issues like
virus software, authentication and an additional 10,000 more things in this
list that occurs when a file is opened.

Why not eliminate this issue altogether with a persistent connection?

We could likely write a book of a 1000 pages of the things that occur when a
windows file is attempted to being opened. From security, to exclusives
locks to viruses software to checking permissions, this list gets so long as
to why even being to try and figure out which one of these issues is the
problem. (why not save that time and money for feeding people or helping the
poor in your town?).