April 27, 2009 at 12:42 pm
Hi
Today My website started running very slowly and in many cases timed out before the sql statement could complete, I restarted the SQL server instance and found that everything began working fine again.
So should SQL Server be restarted on a frequest basis, say once a week to help stop this kind of slow down happening again?
Cheers
Matt
April 27, 2009 at 1:13 pm
Matt (4/27/2009)
HiToday My website started running very slowly and in many cases timed out before the sql statement could complete, I restarted the SQL server instance and found that everything began working fine again.
So should SQL Server be restarted on a frequest basis, say once a week to help stop this kind of slow down happening again?
Cheers
Matt
No, Restarting the machine is not the solution to speed up your sever. Some businesses cannot afford server restarts unless they have a maintenance window to do so. For the start yes it seems to be a hassle free idea but as your website grows there would be a need where you cant afford to restart your sql server anymore.
The best way is to to trace up your server and see whats exactly happening at that time. I am sure there could be blocking issues on your server. Identify the queries that are running at that time and tune the queries for optimal solution.
You also need to give us more details about your server configuration Memory, Disks, sql edition/version, windows edition/version etc..
April 27, 2009 at 1:49 pm
Most of the systems I've run were rebooted less than once a quarter, some once a year without issues.
April 27, 2009 at 2:39 pm
I remember running SQL Server 6.5 and having to reboot the server once a week whether we wanted to or not.
But no, with SQL Server 2000/2005/2008, I would not suggest rebooting the server. Like Steve, I'm rebooting once a quarter or less on most machines. We schedule an annual power down just to cycle machines that haven't been cycled all year long. You frequently find bad components that way.
You may have had blocked processes or some user chewing up all the resources. Rebooting "fixed" the problem, but only until next time. Better to find out what the process or user was doing so that you can prevent that problem going forward.
"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
April 27, 2009 at 3:05 pm
Steve Jones - Editor (4/27/2009)
Most of the systems I've run were rebooted less than once a quarter, some once a year without issues.
We end up restarted our servers on an average of every other month. Then again, we are fairly aggressive in applying OS patches on our Windows servers and they seem to always want to restart the system after applying the patches.
This generally does not affect our critical 7/24 systems - because those systems are clustered and the failover is hardly ever noticed by the end users. Most of the time, all they ever know is that sometime between 1am and 6am the system froze for a few seconds. But again, most of the time they don't notice a thing.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 27, 2009 at 3:20 pm
Matt (4/27/2009)
Today My website started running very slowly and in many cases timed out before the sql statement could complete, I restarted the SQL server instance and found that everything began working fine again.So should SQL Server be restarted on a frequest basis, say once a week to help stop this kind of slow down happening again?
It all depends on how stable your system is considering your system stability depends on the quality of your hardware + how stable is your O/S + how stable is your RDBMS.
I've seen well designed, carefully tunned WinTel+SQL Server systems supporting IVR, PBX and Paging-encoding applications performing like the first day after two years of being powered on; I've also seen systems that required a weekly recycle.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.April 27, 2009 at 3:34 pm
Thanks guys, I was hoping that it was normal practise to restart on a weekly basis, but it looks like I'll have to try and diagnose the problem, or I could just bury my head in the sand and hope the problem goes away by itself 😉
April 27, 2009 at 3:42 pm
Matt (4/27/2009)
Thanks guys, I was hoping that it was normal practise to restart on a weekly basis, but it looks like I'll have to try and diagnose the problem, or I could just bury my head in the sand and hope the problem goes away by itself 😉
You could try that - although I have never found it to work myself...:hehe:
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 27, 2009 at 5:43 pm
Matt (4/27/2009)
weekly basis, but it looks like I'll have to try and diagnose the problem
Could be bad indexing check that out, fragmentation levels, update statistics.....Just defragging the indexes might give you considerable performance.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply