flugaurj
asked on
Microsoft Access 2007 slow on Server 2008 (Terminal Server)
My question is why is Microsoft Access slow on Server 2008 (Terminal Server)? We have a couple of databases that are split into a frontend and backend database and when we run them on Terminal Server 2003 they are lightening fast but when we run them on TS 2008 they are extremely slow in all aspects (loading forms, reports, etc). Is there something we can do to speed these databases up on TS2008? The way the DB's are setup is that the frontend is on the users desktop and the backend is on the file server. I am running XenApp5 on the server as well. The 2003 Servers are running XenApp 4.5. Thoughts?
There is a hotfix that has helped me out.
http://www.mskbarticles.com/index.php?kb=974609
Make sure you have disabled IPv6
http://www.mskbarticles.com/index.php?kb=974609
Make sure you have disabled IPv6
ASKER
Did the Hotfix actually speed things up for you?
I didn't install for an Access based DB but I did with a SQL and it did speed things up.
ASKER
The patch didn't work, Access 2007 still runs super slow on Server 2008 with XenApp5 on top
Are you getting any errors at all in the Event log?
ASKER
No, there are not any errors in the event log...
might by out of order but have you checked firewall settings on 2008 server as that could be culprit. I once had a nightmare with speed as it was dead slow but it was all down to the firewall causing the delays.
ASKER
The firewall is disabled on both servers (Citrix and File)
ASKER
I tried applying the Hotfix in link 1 already, links 2 and 3 don't have anything in them that pertain to my issue and in link 4 the status bar is already unticked.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
<<There were about 4000 records in the table and we deletec half of them. Is there a way to index any of the data to speed up access times?>>
I think the implication of your question was that nothing had changed from 2003 to 2008, yet performance had gone down the tubes and that's what people were focused on.
Of course there are many things you can do to speed up the app itself. And 4000 records is really nothing. Unless the app is very poorly designed, deleting 2000 records should have made very little difference.
I think your problem lies else where. For example, you are running a compact and repair on a regular basis correct?
Please open new questions to explore that and other issues you may have.
JimD.
I think the implication of your question was that nothing had changed from 2003 to 2008, yet performance had gone down the tubes and that's what people were focused on.
Of course there are many things you can do to speed up the app itself. And 4000 records is really nothing. Unless the app is very poorly designed, deleting 2000 records should have made very little difference.
I think your problem lies else where. For example, you are running a compact and repair on a regular basis correct?
Please open new questions to explore that and other issues you may have.
JimD.
ASKER