|
-
Oct 31st, 2008, 03:49 AM
#7
Re: SQL Server Best Practice
Yeah... reboot's should only be when there are problems with the server...
Memory leaks... conenction timeouts etc. and it has been deemed by the business (via advice from IT Support) that a reboot is recommended... normally out of hours to lessen the impact to the business, with a email beforehand send out to communicate with the business.
I would be worried if i worked in a company where there want to reboot for 'the heck of it'!
Last edited by kevchadders; Oct 31st, 2008 at 03:53 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|