The size of the calls table has no affect on the performance/speed of
> But I think there must be a structure like the one done on Calls (RadiusNT
> load all column info at startup)
> RadiusNT can load all columns on serverports table at startup, and then
> collects that data from the radius request,
> then updates serverports (not callsonline)
The CallsOnline IS the serverPorts Table. RadiusNT itself will not be
using the CallsOnline in the next major release (it will update the
> Why not ?
> Is not that a good idea ?
This is a good idea for manual calls update, but for MSSQL, its
irrelevant, since RadiusNT doesn't handle updating the ServerPorts
or CallsOnline view if you are using a trigger.
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart