February 22, 2011 at 9:17 am
well...I ain't doing this for free...
I work FT as a developer, and have touched on all aspects of SQL at one time or another; but i don't foray into maintenance and overall systems health too often.
take a look at my checklist and offer any suggestions, please.
a friend of a friend asked me to look at someones server, because one specific app running on it is running slow. It's a small office, maybe 10 people, with an in house Small Biz SQL Server. I'm assuming that 90% of my time will be looking at indexes and dmv's, but I wanted to be ready for anything.
I have zillions of scripts for various issues...so I just wanted a sanity check... I have arranged my plan and all my scripts in a nice little package, ready for me to do the following, but wanted advice for anything I might have glossed over:
Here's my plan:
1.Check how much hard drive space the server has. Make sure it’s not running out of disk. Check and make sure the OS is not being hammered by some process.
2.make sure there are backups: If not, make some COPY_ONLY FULL backups of each database before getting started.
3.make sure there is a maintenance plan in place. If Not, create one.
4.make sure the production database has no errors. dbcc checkdb, and panic if there is an issue. Repeat for other databases if they want them done also.
5.check to see if statistics are out of date. update statistics based on my script.
6.Check dmvs for missing suggested indexes.
7.Check the dmvs for slowest queries.
8. run a DMV trace to catch all queries, so I can at least identify some performance issues we could forward to the third party application vendor.
Lowell
February 22, 2011 at 9:34 am
sp_blocking
and run the profiler checking reads, writes ,duration
run the standard reports for average io, average cpu
February 22, 2011 at 10:22 am
Lowell, I worked for a small software company that used SQL Server on the underside for a ton of small "mom and pop" operations (five to ten users). 90% of these customers used a third-party "tech" instead of an in-house for budgetary reasons. Of those that used a third-party, the "tech" suggested Small Business Server as the most economical way for them to do business.
I can't tell you how many times I would get called in due to a latency issue within our application and SQL Server. One of the first things I would do when I connected in was to see if they had any other application running on that Small Business Server - low and behold they would have the built-in Exchange turned on as well and the box only had 4-8 GB of memory.
My very next step would be to call the owner of the company and explain the need to get SQL off of that machine immediately and explain how you should NOT have to memory intensive applicaitons running on the same machine. They in turn would call the "tech" who would argue that Microsoft created SBS for just this reason.
Long story short, please take a look at the environment, in particular the applicaitons running on that SBS
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply