But how often? You will get that occasionally, it just shouldn't
be happen often.
> Checked on triggers on the calls table - looked under the 'triggers' for the
> calls table and found nothing! Where should we find them, and what
> triggers should be there?
If you have manual calls update enabled in the RadiusNT Admin, you
don't need the trigger. The trigger is in the radiusnt.sql script.
> We created an Index as suggested by Mike Miller in a post on 3/17/99 as
>
> CREATE INDEX index_AcctSessionId ON Calls(AcctSessionId)
>
> This was done earlier - we have had several 100% CPU incidences since!
That index would only be useful if you search/update records
based on the AcctSessionID field alone (which will never happen).
I wouldn't recommend having it on the Calls table.
> We have been using the Access DB version of RadiusNT since you first
> introduced it - we have had to do absolutely no maintenance on the system -
> since we introduced MS SQL we have had to spend a lot of time learning
> the internal problems and specifics of SQL - I'll be glad to get this to settle
> down again!!! I'm thinking that maybe MS SQL was not the best choice -
> maybe we should have considered ORACLE?
I invite you to grab and Oracle eval and try. I'm pretty sure you would
change your mind. SQL Server for an admin point of view is a lot
better than Oracle.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com