Solved

how often to reboot

Posted on 2013-05-20
5
319 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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:Ramesh Babu Vavilla
Ramesh Babu Vavilla 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

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

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

Naughty Me. While I was changing the database name from DB1 to DB_PROD1 (yep it's not real database name ^v^), I changed the database name and notified my application fellows that I did it. They turn on the application, and everything is working. A …
How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

688 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