Best Practice Reboot Schedule

Is there a best practice reboot schedule for Windows 2000
with SQL Server 2000?
And if they are clustered is the schedule any different?
Previously I used a once a week reboot schedule for
Windows NT / SQL Server 7.You should only have to reboot if you install, say, a
patch that needs to have your server rebooted such as a
SQL Server service pack. And a cluster is the same.
Don't reboot unless you see a need ot.
>--Original Message--
>Is there a best practice reboot schedule for Windows 2000
>with SQL Server 2000?
>And if they are clustered is the schedule any different?
>Previously I used a once a week reboot schedule for
>Windows NT / SQL Server 7.
>.
>|||Darrell Deck wrote:
> Is there a best practice reboot schedule for Windows 2000
> with SQL Server 2000?
> And if they are clustered is the schedule any different?
> Previously I used a once a week reboot schedule for
> Windows NT / SQL Server 7.
You should not need to reboot to schedule on Windows 2000
(unlike NT). But in a clustered situation it is a good idea
to swap over now and then to check the other node is "valid".
We do this monthly at one site. Against weekly for the NT4 boxes.
Regards
AJ