Solved

how often to reboot

Posted on 2013-05-20
5
313 Views
Last Modified: 2013-05-23
for a commercial sql server what is the recommended interval for reboots?
1 week/ twice a month/once a month etc.. what are the benefits to do it often (every weekend) versus more spreadout?

does this depend on how much cores/memory the machine has? or a general principles that is applicable for any sql server?

thanks
0
Comment
Question by:25112
5 Comments
 
LVL 10

Assisted Solution

by:bigbigpig
bigbigpig earned 100 total points
ID: 39181065
I only reboot my Windows servers when patches or other updates require it.  I do not have them scheduled on a set interval.  I cannot see any benefits of rebooting a SQL server on a set schedule if it's not necessary.
0
 
LVL 25

Assisted Solution

by:Lee Savidge
Lee Savidge earned 100 total points
ID: 39181067
Why would you do a scheduled reboot at all? On a production server you wouldn't reboot unless you had to.
0
 
LVL 13

Assisted Solution

by:Alexios
Alexios earned 100 total points
ID: 39181079
Unless it is really required you don't need to do it regularly. Few situations which requires Sql Service restart,

- If the tempdb grows abnormally and fills the disk space (you cannot even shrink), restarting Sql Server will help as tempdb will be recreated.
- Applying Hotfix/Patches/Service packs will require reboot
- Port change etc will require service restart
0
 
LVL 10

Assisted Solution

by:sqlservr
sqlservr earned 100 total points
ID: 39183726
it not necessary to restart SQL Server unless and untill windows patching or SQL Server patching is done.
0
 
LVL 12

Accepted Solution

by:
sachitjain earned 100 total points
ID: 39186438
With my experience I would suggest that you should reboot atleast once in a month. But other major maintenance activities that you need take care of include:
1.> Keep on applying all latest patches and service packs to your server's operating system.
2.> Have a legitimate backup plan in place for backing up databases and transaction logs
3.> Have maintenance plans or jobs in place for updating statistics and reorganizing/rebuilding indexes for all tables in all databases.
4.> Keep regular check on server level and sql instance level error logs. System's performance could be influenced by frequently occuring errors also.
5.> Perform regular database consistency checks over your database

These measures would help you keeping your databases in good shape.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is basically a blog post I wrote recently. I've found that SARGability is poorly understood, and since many people don't read blogs, I figured I'd post it here as an article. SARGable is an adjective in SQL that means that an item can be fou…
If you have heard of RFC822 date formats, they can be quite a challenge in SQL Server. RFC822 is an Internet standard format for email message headers, including all dates within those headers. The RFC822 protocols are available in detail at:   ht…
A short film showing how OnPage and Connectwise integration works.
Need to grow your business through quality cloud solutions? With everything required to build a cloud platform and solution, you may feel like the distance between you and the cloud is quite long. Help is here. Spend some time learning about the Con…

929 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now