disadvantage of frequent reboots

would there be any specific disadvantage to reboot sql server often?
LVL 5
25112Asked:
Who is Participating?
 
David ToddConnect With a Mentor Senior DBACommented:
Hi,

While its not a bad thing, its not a good thing either.

If a personal PC doesn't restart, there is little to no impact.

If a server doesn't restart, who is there to catch it? Do you have lights out management on your servers - each manufacturer calls them something different - and can power the server up remotely, or does it require a human to put big fat finger on red button to power the server back up?

So, if you are doing this every week, sooner or later the server will fail to restart, and then you'll have an extended outage that could be very bad for business.

My few thoughts ...

Regards
  David
0
 
25112Author Commented:
the management has the policy that a reboot every saturday night helps. .this may be true for personal pcs..

but is there any specific disadvantage from sql server's perspective? to do a scheduled reboot every 7th day?
0
 
Surendra NathConnect With a Mentor Technology LeadCommented:
unless, your sql server is storing data, which will be used by an online client at the scheduled re-boot time, there should be no issue.

i.e. imagine google is storing data in your sql server and you re-booted your machine and the while google website goes down for that period of time, until your machine is back.

Apart from the above scenario, there are cases where if there are any uncommited transactions and database restores happening, or any other data base activity will get affected and even  some of the database may get corrupted because of this....

But if you can ensure that no users are getting to the server at that period then there will be no issue at all.
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
Scott PletcherConnect With a Mentor Senior DBACommented:
The main thing would be that the SQL system will be much slower at restart initially because all caches and buffers have been flushed (obviously, since the re-boot loses everything that was in RAM before).  All code must be recompiled and all data read from disk rather than from a buffer.

Presumably it wouldn't affect a scheduled job, since you presumably avoided doing a planned reboot at the same time a (critical) job was supposed to be started.

Any other applications/code extensions would also have to reloaded from scratch, which might slow them down as well.
0
 
jogosConnect With a Mentor Commented:
adding to all of the above

Less weekend-time left for non disturbing maintenance like backup or optimizing your sql  by keeping your indexes  in shape.
0
 
25112Author Commented:
good points- will be useful- thx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.