Re: [RadiusNT] Radius NT 2.5 & SQL 7.0 compatibility issues, deadlocks

Dale E. Reed Jr. ( (no email) )
Wed, 10 Mar 1999 00:19:48 -0800

Mike Miller wrote:
> The only way to temporarly fix the problem we have found is to completely
> drop and recreate an empty calls table (obviously not a good solution).
> After doing so radius will run fine and insert records in the calls table
> for several hours, but after that period of time the problem arises again.
> We are getting the same results with both our upgraded database, and a
> freshly created database used to attempt to diagnose this problem.
> Does anyone know what is going on here and how to fix it?

Have you tried running a checkdb on it? Also, check your indexes and
make sure the stats are up to date. The latest checkdb.sql includes a
cursor to update all indexes of all tables in the Emerald database.
I've been using SQL 7.0 for about a month and haven't seen this before.


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

For more information about this list, including removal, pleasesee this URL: