rebooting server

  • Is it necessary to reboot sql 2005/2000 periodically?

    (How do people handle this- this is more a preventative maintenance question than anything else)

  • I guess this very much depends upon the criticality of the databases hosted. As for us well we get downtime once a month for MS patching etc. So all SQL servers are rebooted once a month. Rarely do we need to reboot them more often unless a specific problem forces us to.

    I'm not aware of the need to reboot them on a regular basis.

    Mark

  • I agree with Mark. SQL Server, even 7 and 2000, when accessed by well-written code should not need to be rebooted other than for server maintenance reasons.

  • Just in case you find yourself needing to reboot a service....not because you'd need to on SQL Server 2005. I've found this platform manages memory much better than in the past.

    We used to reboot SQL and SSAS nightly, not because we had to, but to make sure we had a clean starting point each day. We had a couple applications that we're the most stable, but have since been patched.

    We used a .vbs script, put in a scheduled task, right on the server. We ran this under

    NT Authority\System account to avoid having to manage password changes.

    Greg E

  • One thing to keep in mind when restarting the SQL Server service or rebooting the server is that your buffer and procedure caches are cleared which will cause the server to be respond a bit slower immediately following the restart\reboot.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply