Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
Baselines
11 posts, Page 1 of 2
1
2
»»
Baselines
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, January 31, 2013 9:29 PM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 11:20 AM
Points: 31,437,
Visits: 13,752
Comments posted to this topic are about the item
Baselines
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1414436
gsmith 7350
gsmith 7350
Posted Friday, February 01, 2013 4:16 AM
Forum Newbie
Group: General Forum Members
Last Login: Friday, February 01, 2013 6:17 AM
Points: 4,
Visits: 24
We autochart KPI's on control charts to watch for trends, special causes, etc. . Most of these charts are X-bar with R-charts with control limits calculated to +- 3 sigma. We also keep track of causes for out of control points or system changes that cause a change in average. We then periodically pareto these for action plans for prevention. The charts also provide an excellent view of the common cause variation which we can develop action plans in attempts to reduce. - greg smith
Post #1414563
richardmgreen1
richardmgreen1
Posted Friday, February 01, 2013 6:03 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Friday, May 03, 2013 1:42 AM
Points: 126,
Visits: 150
I've got a spreadsheet which reads a few tables I've set which tracks CPU usage (for now).
I haven't got it set to read disc I/O or anything else at the moment, but it gives me a rough idea of the cause of the slowdown.
It's shows the last 12 hours, by day/hour, by hour and by day.
It also tracks current running queries and any of those queries which don't conform to our best-practice documents.
It's a bit basic but it works for me.
Post #1414618
Eric M Russell
Eric M Russell
Posted Friday, February 01, 2013 7:22 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 9:21 AM
Points: 1,164,
Visits: 3,340
The first I look at are blocked processes, query wait times, and wait types, which can also be baselined just like CPU and I/O. Blocking and waiting are normal in a relational database, and when it extended beyond a certain point, it's perceived by users as "slowness".
"Wise people understand the 10,000 things without going to each one.
They know them without having to look at each one,
and they transform all without acting on each one." - The Tao Te Ching: Verse 47
Post #1414667
sturner
sturner
Posted Friday, February 01, 2013 7:36 AM
Ten Centuries
Group: General Forum Members
Last Login: 2 days ago @ 12:33 PM
Points: 1,315,
Visits: 2,887
I am sampling key performance counters from all my primary production servers every 15 minutes and save 60 days worth of this history. We have other snapshot audits that will trigger on high thresholds of CPU or Blocking etc. Having the historical context provides the forensics to help resolve issues if and when they do happen.
The ones that we have seen so far have correlated to new versions of software put into production.
The probability of survival is inversely proportional to the angle of arrival.
Post #1414676
Miles Neale
Miles Neale
Posted Friday, February 01, 2013 9:14 AM
SSCommitted
Group: General Forum Members
Last Login: Monday, May 20, 2013 9:51 AM
Points: 1,891,
Visits: 936
DBA monitors on an ongoing basis. We have metrics on what is normal for each production server and watch for spikes. It is a normal part of the job.
Not all gray hairs are Dinosaurs!
Post #1414730
Mark Stacey
Mark Stacey
Posted Friday, February 01, 2013 10:05 AM
SSC Rookie
Group: General Forum Members
Last Login: Yesterday @ 4:27 AM
Points: 44,
Visits: 140
Averages can be misleading, you could have a server idling for 16 hours, and breaking for 8.
A better technique is to have buckets with how long the server is in that state.
A histogram for a day showing CPU at 0-20, 21 to 40, 40 to 60, 60 - 80, 80 to 100 with how long it spent there is one way of doing it
Post #1414750
djackson 22568
djackson 22568
Posted Friday, February 01, 2013 10:59 AM
Old Hand
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 8:56 AM
Points: 310,
Visits: 470
I absolutely love the concept of the Stairways series. I don't use all of them for various reasons, lack of time being the biggest, but the fact that they are there for reference when I need assistance is simply outstanding. Thank you to everyone who contributes to these.
Dave
Post #1414766
foxxo
foxxo
Posted Sunday, February 03, 2013 11:48 PM
Say Hey Kid
Group: General Forum Members
Last Login: 2 days ago @ 6:13 PM
Points: 712,
Visits: 1,053
I use an automated baseline / performance monitoring tool rather than manually baseline.
Post #1415123
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Monday, February 04, 2013 5:08 PM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 11:20 AM
Points: 31,437,
Visits: 13,752
Mark Stacey (2/1/2013)
Averages can be misleading, you could have a server idling for 16 hours, and breaking for 8.
A better technique is to have buckets with how long the server is in that state.
A histogram for a day showing CPU at 0-20, 21 to 40, 40 to 60, 60 - 80, 80 to 100 with how long it spent there is one way of doing it
That's interesting. Want to write this up for others?
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1415533
« Prev Topic
|
Next Topic »
11 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.