Actually, I once had a similar problem with SQL database size and never
really did get a completely straight answer as to why. I finally fixed
the problem in the process of fixing something else as well.
As it turns out, in my case because I was running both Ascend boxes and
a USR Netserver I on the same Radius, I either was getting continuous
requests from the Ascend boxes for accounting even though Radius was
seeing them properly, or if I turned on require secret for accounting in
Emerald admin (which the Ascend boxes appear to *require* to stop
sending the requests after Radius saves them in the SQL database) I
couldn't see the USR with Radius. The end result was two seperate
copies of Radius. A side result ended up smaller database size. After
running 2 copies I was able to rid the "duplicate in calls" SQL error.
Originally I filled a 500MB database in less than a week. Now after 2
weeks, I stand at about 40 MB used. My guess is that even though the
calls were logged, the Ascend boxes didn't know it and kept resending
the accounting requests, which were going somewhere else in the database
(error logs??) instead. My suggestion is to make sure no SQL errors are
showing in debug mode on Radius. Don't know if this info will fix your
particular problem, but it may help others. Dale says the duplicate in
calls problem is fixed in RadiusNT 2.2... still waiting to see it.