Since RadiusNT was the ONLY app running on the machine, that's the
reason I singled Radius as being the possible culprit for the memory
problem. Naturally, ODBC could also be the source of the problem.
>It would depend on what else you are doing with the machine
>and the numbers of users. 128mb of Physical memory should
>be fine for most setups, assuming a dedicated machine for SQL
>Server (with no local user logged in).
We have two seperate machines for SQL and RadiusNT
Our SQL Server is a P-II (450) with 384Mb RAM, RAID 5 Ultra/2 SCSI
Our Radius NT is a P-II (400) with (now) 256Mb RAM, Ultra/2 SCSI
All on a 100Mb switched network.
And all the ODBC drivers are the most recent release from Microsoft.
---Graeme Slogrove, BSc (Eng) Elec (Wits)Director, Systems Development & Value Added ServicesNetActive InternetTel: 011-719-0333 Fax: 011-719-0444Support: 011-719-0300
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart