July 23, 2011 at 8:10 am
Hi All,
We are having a yearly mains supply check, therefore I would need to check for the availability and the health of the SQL Server. I would like to know what the nessessary steps to make sure everything is stable as possible please.
Thank you in advance
July 23, 2011 at 12:46 pm
tt-615680 (7/23/2011)
Hi All,We are having a yearly mains supply check, therefore I would need to check for the availability and the health of the SQL Server. I would like to know what the nessessary steps to make sure everything is stable as possible please.
Thank you in advance
It's way to large a subject for a simple forum answer. I'd recommend you do a web-search for "SQL SERVER HEALTH CHECK".
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 6:27 am
Not a comprehensive list by any means; however, this is where I start for server / instance:
Available Memory
Buffer Cache Hit Ratio
Page Life Expectancy
Page Reads per Second
Page Writes per Second
File system latency measured as Free List Stalls
File system latency measured as Lazy Writes Per Second
Average Latch Wait Time in milliseconds
CPU Utilization
Number of User Connections
Measure these over time to get trends then, there's query and data analysis.
There are several very good sources available via Google that, when taken together, form the basis of an excellent periodic system check strategy. IMHO, snapshot statistics do not provide realistic metrics everything must be measured over time.
July 26, 2011 at 6:33 am
pretty wide wave of the hands.. "how to i check my server's health"
You'll probably want to define what you want to check, first, as Jeff said. We can help with details, but not so much on such a wide open question.
GreyBeards got a great point...if you don't have a baseline for your server, you cannot say whether its doing good or bad for many of those perforamnce metrics.
I'd also lean towards using Brent Ozars Blitz 60 minute takeover scripts[/url] to identify anything that was neglected and fallen throug the cracks.
Lowell
July 26, 2011 at 8:34 am
On a lot of our servers, we like to keep performance traces running throughout the year. This allows us to look at a few reports to check on long running queries, consistent blocking, etc. Here is an article that describes the basics for setting up a performance trace and getting it loaded into a table:
Once you have the data getting loaded in a table on a daily basis, it is pretty easy to create a report off it.
Jason
Webmaster at SQL Optimizations School
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply