For the most part, it doesn't matter.
> Heres the big picture: Two Radius servers on separate machines(p-166, Dual
> P-200). Each machine is also running SQL Server. Both Radius DSNs point to
> the primary (p-166) server which replicates the user information (not
> accounting, due to machine stress) to the secondary (P-200's) server in
> event of emergency. Should we have a separate machine dedicated to running
> the Radius Service? SQL Server has been an extreme pain with little
> failures here and there, but I think our size will not allow us to go back.
> During peak times the primary server is feeling quite a bit of stress. What
> is the general opinion on running a SQL database on mirrored hard drives?
> Is the extra write cycle killing performance?
Use the performance monitor shortcut in your SQL Server group to check whats
going on. I usually add cpu used, memory available, and pages/sec to the
list. How much memory does the machine have and how much memory is allocated
to SQL Server? Typically, SQL Server likes LOTS of memory. I would recommend
ATLEAST 64mb of memory to it, and another 20-30 for your tempdb in ram.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com