Re: [Emerald] Consolidation

Dale E. Reed Jr. ( (no email) )
Wed, 05 May 1999 10:38:03 -0700

Jeffrey Stevison wrote:
> OK. I Went into Emerald Admin and ran the Update calls. Not sure why I
> have to do this since I did not upgrade from 2.1, I installed 2.5 with fresh
> database. Anyway, I went in and tried to do the consolidation again, and
> now I get a different error. "SQL error adding CallHistory Item" and it is
> not consolidating.

In order to provide a method of consolidation that does not tie
up your SQL Server during consolidation, we broke out the one step
consolidation into three steps. The Update Calls in the admin
Updates your Call records to put the AccountID and ServerID of the
respective user andm terminal server into the Call record. This
allows for about a 10x faster processing of call records during
the actual consolidation, versuses trying to match the string login
and NASIdentifier fields.

If you remove the key from the Callhistory table in Enterprise
manager, the consolidation should run just fine. To remove
the key, open up Enterprise Manager, Find the CallHistory Table
in your Emerald Database, select Edit, click the Show Advanced
button on the toolbar, and on the first tab, Primary Key,
click the remove button and the click save.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.