(RADIATOR) SQL Server Timeout

[Hugh Irvine]

Hello Ben -

I would start by checking a trace 4 debug from Radiator to see what sort of 
response times you are getting for your SQL queries, then I would look at the 
indexes on the database tables and perhaps add/adjust as neccessary.

I would also check what other processing is occuring on the database at the 
time the problems occur. Ie - are you running some big report or something 
that is tying up the database?

regards

Hugh


On Monday 12 November 2001 18:46, Benjamin Wakefield wrote:
> We're using Radiator together with Platypus Billing System.
>
> Radiator authenticates from the Platypus database, which is running on NT4
> and Microsoft SQL Server 7.0 SP3.
>
> Lately, we have been getting a lot of timeout problems between Radiator and
> the SQL server.
>
> We started noticing it just after we upgraded the SQL server from a Pentium
> III 700Mhz with 256mb RAM to a dual processor machine with 1Gb RAM.
>
> When the new server was built the latest version of everything was
> installed, I thought there might have been problems with the new Microsoft
> Data Access Components (MDAC). So I rebuilt the server and installed the
> previous version. We still get the timeouts.
>
> We thought maybe there were problems with the hardware in the new server
> and replaced components one-by-one, and still get timeouts.
>
> Radiator and SQL Server were running on the same machine. We separated
> them, moving Radiator to a single processor machine with 256MB RAM that had
> nothing installed except Radiator. We still got timeout errors.
>
> We have now moved the SQL server back to a single processor machine with
> 320MB of RAM and we got more timeouts today.
>
> None of the Platypus clients ever receive timeout errors, Radiator seems to
> be the only thing that queries the database that get "time out".
>
> I really don't know a lot about SQL server, when it was originally
> installed we didn't do anything more that a typical install and everything
> was fine, until we moved to a different machine!
>
> Are the SQL timeouts normal? Should they happen on a daily basis? Did we
> just not notice them before?
>
> If anyone can shed any light on this I'd really appreciate it!
>
> Regards,
> Ben
> ______________________________
> Benjamin Wakefield
> ben at team.dcsi.net.au
> http://www.dcsi.net.au/
> DCSI - We do Internet.
> 71 Victoria Street
> Warragul, VIC 3820 AU
> Ph: 1300 66 55 75
> Ph: +61 (3) 5622 2980
> Fx: +61 (3) 5622 2998
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.