Access XP slow on 2003 Terminal Server

[Bill]

We have an access xp application tied to a sql 2000 backend. After moving to
a clean install of windows 2003 sp1 from windows 2000 server the application
slowed down noticably and the number of odbc errors increased.

I have tried:
- installing a 2003 server and converting to access 2003
- moving the backend to a sql 2005 server
- running access in 2000 compatability mode
- tuning odbc settings and connection pooling.

I have not had much luck finding existing information on this problem. Any
suggestions would be greatly appreciated.

 

[aaron.kempf]

1) upgrade it to SQL Server
2) run profiler and then the Database Tuning Advisor (a component in
SQL Server developers' edition)

MDB isn't reliable enough for a single user and a single record.

spit on anyone that uses MDB in the year 2006.
that disease (stupidity) might be contagious


-Aaron

 

[Tony Toews]

1) upgrade it to SQL Server

He is running SQL Server.

MDB isn't reliable enough for a single user and a single record.

Wrong.

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

 

[aaron.kempf]

he isn't trying the SQL Server route adequately.

once he makes a decision about which route to go-- he just needs to
tweak the performance.

with sql server developers' edition; it is easy to run the Database
Tuning Advisor.

this is considerably cheaper; faster and more performant than anything
involving Access MDB files.

 

[Bill]

Do you have any insight into the problem Mr Toews?

 

[aaron.kempf]

are you really going to trust that Tony Toews asshole with information
about SQL Server?

he is a MDB baby.

-Aaron