Server Reboots

[MasterRacker]

We have a vendor that claims they can't guarantee the stability of their product (web/Java client, SQL 2000 server) unless we reboot our SQL server at least weekly if not more often. We've always felt this was ridiculous and since we have more than one DB on the server, it's unacceptable anyway.

I'm taking a couple of classes online through a local college that recently switched from Blackboard to D2L and they just issued a bulletin about D2L problems they are controlling by rebooting their SQL server daily.

Assuming the SQL server is only running SQL Server and hosting databases (no other applications) just what kind of application can cause a SQL server to need rebooting? CLient machines and other types of application servers needing reboots, yes - but I've never heard of database servers needing this.


Jeff
The future is already here - it's just not widely distributed yet...

 

[mrdenny]

It's usually do to poor coding on the Application side. They will pull to much into memory on the SQL Server, and never let it go away, or poorly coded extended stored procs, and the like.

There is no reason from the SQL side to need to reboot the server more often than is needed to patch SQL and Windows.

One thing I've noticed is that the connection pools that some people are using especially with Java suck big time, and will open tons on connects to the SQL Server and the only way to clean everything up is to stop and restart the SQL Server because the java connections through the JDBC connector aren't being closed correctly, thus wasting CPU, and memory on the SQL Server.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[timscronin]

One of the gains of keeping sql server up is that it stores optimized plans on how to get the data (through sp's or just sql statements), when you reboot, that is lost.