GasGiant
|
Our terminal server is in the same rack as our PSQL server. TS users have a better "user experience" (faster program operation) than network users, especially with searches and reports. Since DBA/Evo uses the PSQL database in a transactional way, a network round-trip is required for each record. The shorter the round-trip, the faster the reports run. That's why I run things like MRP, BOM roll-ups (BM-G), Update Costs (IN-L-E) and Rebuild Stock Status (IN-L-E or IN-D) directly on the PSQL server. That being said, there are some downsides to Terminal Server use. Firstly, don't use this method to run DBA Classic. Classic will max out CPU usage each time it runs a command. Huge delays are experienced once you hit the third user session on the TS. Another thing to watch for is users closing the RDP window without closing Evo first. They can leave stray sessions open and gobble up licenses. I had one user who kept closing the RDP window and opening new ones throughout the day. One day she had six licenses tied up at the same time! We have since put in a Cytrix server, which eliminates the multiple sessions, but I still have to clear sessions from internal users sometimes.
|