|
| | | Forum Newbie
Group: Forum Members
Last Login: 10/24/2008 12:06:00 PM
Posts: 8, Visits: 15 |
| Tell that "Tech Team" to go blow themselves. Im a Network Admin, in charge of a clients PDS theyve been using PDS with SQL Express 4GB RAM system (even though SQL Express only uses 1GB of that at most) it allows the servers load to have plenty of legroom. There are approx 50 users here all with Point installed on their local workstation strung across various sites 4-5 locations) who access the PDS server at the main office along with local users at the main office. We've been running Point since 5.4 and have loans from 2003-200x (Im not onsite to tell you the total sizes) but with your numbers Im sure your well within range.
Full SQL Server is not needed at that small a level. If your talking 500+ loans a month over 100 users or more then maybe you could consider it but even then I doubt it. Point doesnt place that great a strain on SQL that its required. If Point used SQL properly there would be less problems involved than they have just using it as more a index/query (but thats another issue.)
PDS is accessed via the local point install over HTTPS a secure web socket connection so as long as there is an internet connection running users everwhere will be able to access it. My question would be why do you want to use a Terminal Service connection to run point? Just have those users install a local workstation copy of point and be done with it (This will also put less strain on both start and end points internet bandwidth, since you must make that connection from one computer to the server (creates 2 loads essentially that arent needed). |
| |
|
|