Re: [Emerald] SPEED
Fri, 29 Jan 1999 10:50:00 -0600

Ah so I guess the size of the tempdb on disk doesn't matter once you
set it in the preferences to be in RAM.

GREAT News!!! That means I can consolidate without having to worry
about moving authentication somewhere else. Thanks Dale!

So what is the 3 step process.
Update Calls in DB Maintenence (only after the upgrade?)

Then Summary.
Then Charges on each of the listings?
Then Trim? ( I did not see anything on trimming in the manual)
Does whether you choose Month or Year or All in the drop down matter
when you click Trim.

On Thu, 28 Jan 1999 18:47:57 -0800, you wrote:

> wrote:
>> Any tips on speeding up Consolidation?
>> Server is a P2-450 with an Ultra-Wide RAID5 Array and 512MB RAM.
>> SQL memory set to 100mb
>> tempdb set to 20mb
>> 10mb of tempdb in ram.
>> The database is quite large, however, it takes a whole day to
>> consolidate. Was wondering if there were anymore sql settings that
>> may help.
>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
>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=20
>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).=20

For more information about this list, including removal,
please see