SIMS, PARS and Terminal Server Recent Slowness
Briefly: We've been running PARS and SIMS .Net under MS Terminal Server on a 2003 SP2 box for about 25-30 concurrent users and all has been fine for well over a year. PARS is used to take registers and this is the only use of the terminal server. Besides security patches, no configuration changes have been made on the TS or sql server since last SIMS update.
We recently upgraded from PARS 2.20 and SIMS June 2008 to PARS 2.269 and SIMS Sep 08 and enabled Windows Authentication for SQL 2005 (as PARS was now using Windows Auth rather than cached sql auth). Yay for changing 3 things at once and making it hard to diagnose issues. :(
Anyway, a significant proportion of my reliable users say that PARS is running slower than previously, some say PARS itself, others say initial login.
Running perfmon on the terminal server and sql server for 24hrs show nothing out of the ordinary - load on the TS peaks and stays a bit high during the initial scamble to log on for morning and afternoon registers but usage patterns are the same as they were pre-upgrade. The SQL server isn't thrashing disks, the buffer cache hit ratio is at a minimum of 99.5%, there's oodles of ram spare and processor use is a maximum of 55%. SQL is also set to take and hold half the ram as a minimum at startup.
Users have a mandatory profile set when using the TS and all unnecessary visual guff is turned off.
DNS resolves correctly all ways, so Windows Auth for SQL shouldn't be bogging it down, though the TS is being noisy (in terms of informational events, not errors) in the DCs security log.
To add to the confusion, a couple of users have said they found it faster. I'm assuming they don't usually log in when lots of other people are on it.
I'm still digging around to see if there's any clues I've missed, but has anyone got any suggestions?