I had months 1-12 (Age Monthly, hit SHOW) listed and I highlighted one
and hit trim and it wiped them all out...now all I show when I do a
show AGE:ALL is month 1 and 12
I know that most of them were between months 3 and 5 or so were
already consilidated before the upgrade.
On a side note I changed my SQL memory to 102400 in server config
options which should give me 200mb since it's in 2k units. Strange
thing is sql memory usage doesn't seem to go above 143448K in
TaskManager.
BTW excellent work on 2.5
Only hitch so far is we will have to go add back service defaults as
it seems to wipe them all out.
Oh one more thing so now that consolidation doesn't lock out people
from authenticating with accounting too are there any processes or
steps in Emerald that will cause people not to authenticate or their
accounting packets not come in while Emerald is doing that process?
I.E. CheckDB? Trim Calls?
On Fri, 29 Jan 1999 10:31:04 -0800, you wrote:
>
>
>iml@interconnect.net wrote:
>>=20
>> 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.
>
>Yes.
>
>> GREAT News!!! That means I can consolidate without having to worry
>> about moving authentication somewhere else. Thanks Dale!
>
>That was one of the main enhacements to the consolidation.
>=20
>> So what is the 3 step process.
>
>The three steps I outlined below.
>
>> Update Calls in DB Maintenence (only after the upgrade?)
>
>You must do that before running a consolidation if you do not have
>the scheduled task that does it automatically.
>=20
>> Then Summary.
>> Then Charges on each of the listings?
>
>Yes.
>
>> Then Trim? ( I did not see anything on trimming in the manual)
>
>Its was a late entry into the Admin.
>
>> Does whether you choose Month or Year or All in the drop down matter
>> when you click Trim.
>
>Yes. What you see in the summary of the trim is what will be removed
>where you select delete. Do SMALL chunks at a time (like each month)
>and not a full year.
>=20
>> >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.
For more information about this list, including removal,
please see http://www.iea-software.com/maillist.html