Vista 2007 slow on network

[GregD]

All:

We are trying to run an mde file from Access 2003 on a Vista PC with Office
2007 SP1. Running the file locally, the mde runs slower than on an XP
machine, but is still reasonable. However, running the mde from a network
server (Windows 2003 R2 SP2 and SP1) is really slow. Form controls respond
slowly, the Ribbon responds slowly, and data access is slow. Often 10X more
slow than a local mde file.
I have read the web and newsgroups and tried all the suggestions:
1. netsh autotunning=disabled.
2. Re-starting the Firewall on the server.
3. Disable IPv6.
4. Ran the Vista internet test to make sure our router was OK.

Still have no luck. At best I sometimes perceive that the form responds more
quickly.

Anything else I am missing?

Thank you,

GregD

 

[aaron.kempf]

MDB / MDE has been giving -ME- unacceptable performance for the past
decade.

Wake up to the 90s and move to SQL Server

-Aaron

 

[Fred]

Aaron's is certainly a minority opinion.

Access works fine. The problem is Vista. I'd upgrade your Vista to XP.
Maybe Vista's replacement (which they said is coming out in 2009) will be
better.

 

[aaron_kempf]

I'm not a minority.

Maybe _IN_THIS_NEWSGROUP_ but that is because anyone else that learned
SQL Server doesnt' give a crap about Access any longer.

I love both.
So I've got to stand up against this MVP Fatwa and stand up for what
is correct. What is optimal.

I will no longer be bullied into submission.

SORRY

-Aaron

 

[Gina Whipp]

I learned SQL Server and use it but ONLY when Clients needs warrant it,
which, in my case is a VERY SMALL percentage. Other then that Access is my
first choice and my first love!

I do not however, feel the need to force an SQL Server down EVERYONE's
throat. I do not feel the need to come into an ACCESS newsgroup and 'bully'
EVERYONE/ANYONE into switching, as I see you do, with half truths ("..It
doesn't work with 10,000 records..." Give me a break, I got databases with
over 150,000 records in 4 seperate tables and have been running for years
and no where near the limit of Access.)

If your love is SQL Server, why do you spend so much of your time in ACCESS
newsgroups, bullying people? Why not go assist people in the SQL Server
newsgroups? All, I see is one 'bullying' attemp
http://www.microsoft.com/technet/co...EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-usand

And one where you, the GREAT SQL Expert asked for advice...
http://www.microsoft.com/technet/co...-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us

Of course, now we'll probably hear how that wasn't you! (And I'm sure I'll
be moved to stalker status, at least I'll be in GREAT company!) Oh well, I
need to get back to my Access database...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

I'm not a minority.

Maybe _IN_THIS_NEWSGROUP_ but that is because anyone else that learned
SQL Server doesnt' give a crap about Access any longer.

I love both.
So I've got to stand up against this MVP Fatwa and stand up for what
is correct. What is optimal.

I will no longer be bullied into submission.

SORRY

-Aaron

 

[Paul Shapiro]

You didn't say if you have separate front end and back end databases? If
not, split the backend (tables) out from the frontend (everything else) and
use linked tables in the front end. Make sure each user is running a local
copy of the front end from their own hard drive, not over the network. If
you're worried about synchronizing FE updates, you could give the users a
shortcut that runs a batch file to copy the latest FE from the server to
their hard drive, and then executes it from there.

You could try creating a version of the mde in Access 2007 SP1 and see if
that performs any better for the Access 2007 users.

Depending on your environment, you might find disabling SMB signing in the
server and client to improve the speed. By default Windows Server encrypts
communications with workstations. Sometimes disabling this encryption helps.

Besides disabling autotuning, you could try disabling the netsh options for
rss (receive side scaling) and chimney (offloading).

 

[Fred]

On the debate, I learned both. Actually, that's a misnomer, unless you use
Access as a front end for teh SQL server, it's learning SQL service plus a
pile of other apps to do what Access does. Now I use both.... Access for
data work, and SQL for impressing people on how smart I am.

Vista is slower than XP, and Office 2007 is slower than 2003. But, from
benchmarks etc. the Vista / 2007 combo should only be twice as slow as the
XP/2003 combo, not 10 times slower.

 

[aaron_kempf]

Gina;

WTF are you talking about?

Just because Microsoft blocks my posts-- does that mean that I've only
made 2 posts?

SQL Server is for _EVERYONE_.

You're the dipshit that is forcing MDB / ACCDB down everyones throat.

I don't need to 'save' people in the SQL newsgroups. They already got
that memo.
For everyone else that is still stuck with a 'Handicapped Database'--
they need to be enlightened.

Thanks-- look forward to hearing you rant and rave about how they do
not 'block my posts'.
Oh wait a second-- the post that you just made? that one where you
attacked me? I dont think that it shows up in the newsgroup reader.

THanks-- that's proof enough for me.

Microsoft censors people that are critical.

I'd rather eat dogshit than let you poor stupid people use Access
MDB / ACCDB another day.

i don't hate Access.
But Accdb / MDB is _NOT_ a database.

-Aaron

 

[GregD]

I know this sounds weird but the solution was related to path length. A
co-worker found something about long paths being a problem with Vista and
networking.
Short paths work. I don't understand why; it isn't like we had a path over
100 characters. Mapping a network drive right to the working folder on a
server yields results almost as fast as running the application locally.

GregD

 

[aaron.kempf]

you shouldn't have to deal with this crap.

Move to SQL Server; they don't care how long your path names are!

I mean; what happens when your network admin moves your folder
around?

-Aaron

 

[aaron_kempf]

Access for 'data work'

What do you mean?

I use SQL Server for 'data work'
I mainly write views, and I have these components that use 'chapters
of queries' to launch a whole ton of queries at once.

SQL Server can handle it.
Access can't.

Apparently you haven't learned Analysis Services.. because anyone that
knows SQL Server would grow into SSAS-- SSAS is by far the most
popular tool for ad-hoc reporting.

-Aaron

 

[Paul Shapiro]

Thank you for sharing the solution. Very helpful.

Maybe mapping the drive keeps the authentication between the workstation and
server current? There have been suggestions to keep a small, static
recordset open in the front end to improve performance. When I tested some
years ago, I couldn't see an affect, but maybe mapping the drive
accomplishes something similar?