First, I would recommend giving 250mb to SQL Server. You can't have
tempdb on both disk and memory. I'd recommand a 48-80mb tempdb in
RAM. The more memory you give to SQL Server, the faster everything
will run.
> At that rate it will take us 2 days to clean up our DB after upgrading
> to 2.5 before we can start authenticating users on it....or can you
> now authenticate with accounting while consolidating?
>
> Another thing I didn't see this in the docs perhaps I missed it...
> What is the Update Calls option under DB Maintenance.
The new 2.5 consolidation is three steps rather than one:
The first includes updating the new records to include the AccountID
and ServerID, based on the Username and NASIdentifier, respectively.
This can either be done using the Admin, Manual Calls or with the
tasks that get installed when you create the database (the insttask.sql
file).
The second part is the actual charge and summary calculations. As
Emerald goes through, it marks the records (the status field) as
being process to prevent duplicate processing.
The third part if DB cleanup, or removing old/uneeded records. This
is also done in the admin, DB Maintenance, trim calls table.
The first two parts both use server side cursors for speed and also
to prevent any long term locking of the calls table like the old
consolidation did.
I did a consolidation on 1 million stop records where the first step
took about three hours and the second took about 2 hours. This was
on a PII-300 with 256mb of RAM and UW SCSI. The whole time I was
running stress tests of RadiusNT 2.5 with only minimal performance
degredation (including both accounting and authentication).
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.comFor more information about this list, including removal,please see http://www.iea-software.com/maillist.html