September 17, 2009 at 5:06 am
Hi,
I am in search of answer to "Why do we need to reboot the SQL server..?" . I have googled this as well but have not found a satisfactory answer.
Scenario is:
I have implemented a maintenance plan on the client system which requires reboot of the SQL server. It is implemented to take care of memory, handle, or process leaks etc...
But now client has come back saying that I have not seen any of the issue in the SQL server then why do we need to reboot the server.
I just want to answer the question...answer need not to be technical but it should give him some accceptable points..
Thanks in advance..!!
Sanjeev.
September 17, 2009 at 5:17 am
sanjeev_krs2004 (9/17/2009)
Hi,I am in search of answer to "Why do we need to reboot the SQL server..?" . I have googled this as well but have not found a satisfactory answer.
Scenario is:
I have implemented a maintenance plan on the client system which requires reboot of the SQL server. It is implemented to take care of memory, handle, or process leaks etc...
But now client has come back saying that I have not seen any of the issue in the SQL server then why do we need to reboot the server.
I just want to answer the question...answer need not to be technical but it should give him some accceptable points..
Thanks in advance..!!
Sanjeev.
As you mentioned, is it a reboot of the physical server or a restart of the sql services. without knowing more details about your maintenance plan, it is hard to say. only thing i can think of, is that doing a reboot would clear down memory and clear out cache, amongst other things . so if your maintenance plan needs to create some form of baseline initially to be utilised for monitoring perhaps maybe.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 17, 2009 at 5:25 am
Hi -
Its just a simple maintenance plan where I am rebuilding indexes, reorganizing indexes, shrink database...etc. All the usual stuff. Secondly, I am not sure but in past I have seen that some issues got resolved after physically rebooting the SQL server.
Thanks,
Sanjeev.
September 17, 2009 at 5:51 am
In that case, I cannot think of any reason why you would do it.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 17, 2009 at 6:40 am
WAY back on SQL Server 6.5, we had to schedule a reboot once a week because that version of SQL Server and the Windows operating system back then were so horrific with memory leaks and other issues, that we just had to.
Flash forward 14 yeas. We run SQL Server systems for months without a reboot and don't have any issues at all. The only reason we reboot most systems is because of security patches or upgrades to SQL Server or to the OS, or because of our annual power down when we bounce everything in the house as a security and maintenance routine.
No, I would absolutely recommend against booting the server on a weekly or monthly basis, just because.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 17, 2009 at 9:33 am
sanjeev_krs2004 (9/17/2009)
Hi -Its just a simple maintenance plan where I am rebuilding indexes, reorganizing indexes, shrink database...etc. All the usual stuff. Secondly, I am not sure but in past I have seen that some issues got resolved after physically rebooting the SQL server.
Thanks,
Sanjeev.
I would not include shrink database in your maintenance plan - if it is growing and then shrinking it will be fragmenting.
September 17, 2009 at 11:59 am
Seth Lynch (9/17/2009)
sanjeev_krs2004 (9/17/2009)
Hi -Its just a simple maintenance plan where I am rebuilding indexes, reorganizing indexes, shrink database...etc. All the usual stuff. Secondly, I am not sure but in past I have seen that some issues got resolved after physically rebooting the SQL server.
Thanks,
Sanjeev.
I would not include shrink database in your maintenance plan - if it is growing and then shrinking it will be fragmenting.
Good catch. I didn't even notice that. Yes, I agree. I'd take that out of the plan as well. That's not a part of the "usual stuff." I don't see statistic maintenance in your list. Do you have that?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 17, 2009 at 10:34 pm
I'm with Grant... you should be able to run a server for years without a reboot. I'm also with the others on shrinking stuff. Don't do it unless you've had a run-away cross-join blow a log out of proportion.
For reindexing in 2k5, you may want to use the "Sort In TempDB" option to keep the logs of the individual databases from expanding during index rebuilds.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2009 at 11:46 pm
Thanks a lot to all of you..!!!
For sparing your precious time and sharing your knowledge...I would definitely keep these points in my mind and will change the maintenane plan accordingly. If any issue occurs again :)...will get back to you guys.....
Thanks,
Sanjeev.
September 18, 2009 at 12:42 am
There are only two reasons why one should stop and restart a sqlserver instance:
- to apply a servicepack/hotfix
- to have tempdb to its original or set starting size ( in case someone just blew up tempdb files by doing huge sorts, ... ). (live shrink may still cause issues)
- you nolonger need to stop/start sqlserver because a process is eating 100%. You can always connect using DAC and kill that process if needed.
(I've had some cases where this caused the spid to be in a rollback state for a long time. I then stopped/restarted the instance to speedup the rollback. I don't advise doing frequently or as "it helped once, so we need to do it every time" !
Other reasons why sqlserver is rebooted is mainly because of maintenance of the os, leaks in other softwares in case of non-dedicated boxes.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply