D
David
Guest
couldn't think of a good short subject line. Here is what I need to do:
currently have one location where a home grown processing application is
used. The app is a ms access (DAO) application that links via ODBC to a sql
2000 server, which houses the actual data tables. The access front end is
very network intensive, not effecient at all. Now, we are possibly going to
open 2 new locations in other states. These 2 new locations need to use this
processing software. I am thinking the best thing to do is setup a terminal
services server in the central office, where the database server is, and
having the new sites use terminal services to use the processing software.
This way we don't have to try to run the app over a WAN (no way) and don't
have to have seperate remote database servers, synchronizing content with
each other. Unfortunately, re-writing the application completely, or even a
new bandwidth friendly http front end, is not an option. I have to make it
work as is.
1) anyone know right off the bat if MS Access (2002) will have issue running
in a TS session? Several of these sessions at once?
2) sizing the server: it takes roughly a 1GHz process with 512MB of ram
(running xp pro) for this app to perform acceptably. In terms of sizing the
terminal server hardware I assume I only need to take into account how much
memory the actual app (access) is using right? Considering the 1GHz, 512MB
needed I mentioned above is the whole client computer, including all the
resources taken by the OS. So I'm assuming I just check out task manager to
see how much memory access is using (at different times etc...) to estimate
how much memory per user will be needed on the TS server? How about
processing power? How would I go about estimating what I'll need for that?
3) what are popular ways people are connecting remote sites these days?
dedicated lines? simple cable modem and vpn tunnels? site to site vpns? I
realize this depends on many things like how many users (bandwidth
requirements) etc.. which I have not given, and that this issue may be
better posted to a different forum... none the less, its a part of my puzzle
and any input would be appreciated.
currently have one location where a home grown processing application is
used. The app is a ms access (DAO) application that links via ODBC to a sql
2000 server, which houses the actual data tables. The access front end is
very network intensive, not effecient at all. Now, we are possibly going to
open 2 new locations in other states. These 2 new locations need to use this
processing software. I am thinking the best thing to do is setup a terminal
services server in the central office, where the database server is, and
having the new sites use terminal services to use the processing software.
This way we don't have to try to run the app over a WAN (no way) and don't
have to have seperate remote database servers, synchronizing content with
each other. Unfortunately, re-writing the application completely, or even a
new bandwidth friendly http front end, is not an option. I have to make it
work as is.
1) anyone know right off the bat if MS Access (2002) will have issue running
in a TS session? Several of these sessions at once?
2) sizing the server: it takes roughly a 1GHz process with 512MB of ram
(running xp pro) for this app to perform acceptably. In terms of sizing the
terminal server hardware I assume I only need to take into account how much
memory the actual app (access) is using right? Considering the 1GHz, 512MB
needed I mentioned above is the whole client computer, including all the
resources taken by the OS. So I'm assuming I just check out task manager to
see how much memory access is using (at different times etc...) to estimate
how much memory per user will be needed on the TS server? How about
processing power? How would I go about estimating what I'll need for that?
3) what are popular ways people are connecting remote sites these days?
dedicated lines? simple cable modem and vpn tunnels? site to site vpns? I
realize this depends on many things like how many users (bandwidth
requirements) etc.. which I have not given, and that this issue may be
better posted to a different forum... none the less, its a part of my puzzle
and any input would be appreciated.