Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

SQL Server 2008 - Worth the Wait

SQL Server’s first significant upgrade in three years features a number of envelope-pushing enhancements and improvements. Which will have the greatest impact on SQL administration and development? More...
Latest Articles

Slowly Changing Dimensions in SQL Server 2005
Audit Data Modifications
SQL Server 2008’s Management Data Warehouse
Same Report but Different Methods in SQL Server Reporting Services ...

More     
 
Latest FAQ's

SSIS Lookups are Case Sensitive
Convert Number to Words in SSRS
After installing SP2 on SQL Server 2005 x64, when trying to ...
Remote Name Could not be Resolved in SQL Server Reporting Services ...

More     
   
Latest Software Reviews

SQL Server DBA Dashboard
SwisSQL DBChangeManager
SQLMesh - SQL Server Search Tool
SoftTreeTech SQL Assistant

More     

Should we automatically reboot our SQL Servers on a weekly basis?


Printer friendly

Question

There's a debate going on within our company about whether or not we should automatically reboot our SQL Servers on a weekly basis. We are not experiencing any current problems, but some people are saying that by regularly rebooting, we will prevent future issues. Will doing so help performance or reliability of SQL Server?

 

Answer

There is a common myth among many IS people that Windows Server software needs to be rebooted regularly for it to work efficiently. There may have been a grain of truth to this in previous versions of Windows NT Server (before 4.0), but since 4.0, there has not been any need to reboot Windows Server on a regular basis.

I have seen many, many Windows servers that are virtually never rebooted, and they never have any problems due to the OS.

On the other hand, I have seen poorly written applications written for Windows Server that have memory leaks that have force the need to reboot the server on a regular basis. But this problem is the fault of the application, not the OS. It is very possible that less knowledgeable IS staff in general have improperly diagnosed the cause of a server's problem and blamed it on the OS, and not the application as they should, which is perpetuating this myth.

Since your SQL Server is not having any problems, leave it alone, and tell the other people on your staff to stop listening to urban legends.



Comments:
Your Name  
Email    
(Emails will not be displayed on the site or used for promotional purposes)
Comment  


Type characters in the image
 
 (case sensitive)

 
 
 







Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views