December 1, 2011 at 9:12 am
Hello all,
I've built a new SQL server and I want to gather some baselines before it goes into production, with the aim of using these as a comparison against future baselines.
Is there a recommended amount of time I should let the data collections run for ? I was thinking around 3 - 3.5hrs, but I'm not sure if this is long enough.
Cheers
Vultar
December 1, 2011 at 9:20 am
I guess I'm not sure exactly what you're testing here.
On a server that's not in use yet, I'd use performance stats from the server it's replacing, if there is one, as the baseline.
Otherwise, if it's not in use, you really won't get performance baselines, no matter how long you run tracking routines.
Or do you mean something else?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
December 1, 2011 at 9:21 am
What are you looking for? If it is not being used, how do you compare? Can you give some more information please?
Thanks,
Jared
Jared
CE - Microsoft
December 1, 2011 at 9:34 am
Thanks for the quick responses.. sorry I should have been a little clearer in my original post.
The 'server', is actually a 4 node 2k8 R2 cluster which is going to be used for a consolidation project. My thoughts were to take a baseline before migrating any dbs, and again after each db migration. Maybe I'm I was wrong in thinking I should be done prior to any migrations ?
As for the stats to be collected, I have a pre-defined perfmon template which I want to run.. I'm just not sure how long I should run the collection for.
Cheers
Vultar
December 1, 2011 at 4:06 pm
Get the free SQLIO tool and gather stats from that too. That will give you a best-case baseline for disk io (and, if the numbers aren't good/right, allow you to immediately correct a poor disk setup, which will kill SQL Server).
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
December 2, 2011 at 2:24 am
Get the free SQLIO tool and gather stats from that too. That will give you a best-case baseline for disk io (and, if the numbers aren't good/right, allow you to immediately correct a poor disk setup, which will kill SQL Server).
I'm working on this at the moment 🙂
Cheers
Vultar
December 2, 2011 at 4:54 am
With bare metal all you can measure is potential. SQLIO is the way to go.
However, if you're consolidating, measure the other servers before you start moving stuff onto the new one. Then you have a before & after to compare with.
Your plan for establishing a baseline is a good one.
"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
December 2, 2011 at 5:16 am
Thanks for your response Grant.. What would you say is reasonable amount of time to measure over ?
Cheers
Vultar
December 2, 2011 at 5:35 am
vultar (12/2/2011)
Thanks for your response Grant.. What would you say is reasonable amount of time to measure over ?Cheers
Vultar
Personally? A week. I like to be able to see the rise & fall as people log-in, etc. But, at least 4 hours of performance metrics at the height of the day ought to give you a good indication of how things are behaving.
"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
December 2, 2011 at 5:49 am
Superb, this gives me a good indication of the minimum time I need to measure over.
Thanks again for your help!
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply