I now have many more of my users using my CHS application on the web and we really experience a big slowdown from mid morning to end of work day. My structure is such that my users all have access to my legacy Access application via Remote Desktop Connection and Terminal Services. For now, I have to keep my new web application on the same server because it accesses the same back end database for each customer as the Access application. I think that the number of users logging on to our servers via Terminal Services is actually what causes a big part of the web slow down.... Does anyone have knowledge that will verify this assumption?
My main question, though, is this.... When users log on via RDC / Terminal Services to use my old Access application, it means that their back end Access database is opened and remains open. Is it possible that when the web application needs to retrieve or update data in that back end database, it is slowed down because the file is open? I know the web application goes there, opens it, does what it needs, and then closes it. But the front end Access application that is linked to the back end data file (one for each customer) may already have the file open. I hope I'm making sense. I'm just asking these questions because I'd like to feel like we will probably have increased speed once I am able to move everything to the web on another server (if I EVER get done developing all the logic!)
My application is a very heavy duty job costing and accounting application, so there will always be a lot of callbacks to the server. I think that there are anywhere from 20 to 40 users using the web application within the same hour during the work day right now.
Any general thoughts or input would be greatly appreciated.
My main question, though, is this.... When users log on via RDC / Terminal Services to use my old Access application, it means that their back end Access database is opened and remains open. Is it possible that when the web application needs to retrieve or update data in that back end database, it is slowed down because the file is open? I know the web application goes there, opens it, does what it needs, and then closes it. But the front end Access application that is linked to the back end data file (one for each customer) may already have the file open. I hope I'm making sense. I'm just asking these questions because I'd like to feel like we will probably have increased speed once I am able to move everything to the web on another server (if I EVER get done developing all the logic!)
My application is a very heavy duty job costing and accounting application, so there will always be a lot of callbacks to the server. I think that there are anywhere from 20 to 40 users using the web application within the same hour during the work day right now.
Any general thoughts or input would be greatly appreciated.
Comment