Disadvantages - assuming you have a switch between the two machines,
performance will be pretty much the same as running on the box. Cost is a
disadvantage, if that's a factor.
Advantages - more memory for SQL server, less load coming from another
process (radius), semi-redundancy ( if running in odbc / text mode, should
the SQL server fail, auth is still possible), ability to prioritize SQL
server and perhaps two or three more.
One point to mention though. RAID5 for a SQL box that is used for Auth and
Accounting (or just accounting) should be avoided. The write performance of
the transaction log suffers immensely due to the slow write performance of
raid 5 (even on a raid card, unless you have write-back cache enabled on the
card, something not suggested anyway) and can negatively affect performance
between radius and the SQL server.
My two cents worth ;)
Regards,
Graeme
---Graeme Slogrove, BSc (Eng) Elec (Wits)Director, Systems Development & Value Added ServicesNetActive InternetTel: 011-719-0333 Fax: 011-719-0444Support: 011-719-0300
-----Original Message-----From: majordomo@essex1.com [mailto:majordomo@essex1.com]Sent: 20 April 2000 07:48To: radiusnt@iea-software.comSubject: [RadiusNT] SQL Server and RadiusNT
I am running RadiusNT Enterprise and SQL 6.5 on the same server at thistime. The system has handled remarkably well in the past, but it isstarting to show degredation in performance. I am planning to move theradius database over to a new dedicated SQL server and wanted to know theadvantages/disadvantages of separating my Radius and SQL server. Note thatthe existing SQL is dedicated to Radius.
TIA,Tomtep@essex1.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart