5 Reasons You Must Start Capturing Baseline Data

Question

5 Reasons You Must Start Capturing Baseline Data

Viewing 11 posts - 16 through 25 (of 25 total)

You must be logged in to reply to this topic. Login to reply

Robert.Sterbal SSCrazy Points: 2855 More actions · Answer 1

I wish I could get the developers here to log some of the baseline data into the database. I often baseline information from tables that have large numbers rows and distinct rows of data in the datetime fields.

Mike Dougherty-384281 SSCrazy Points: 2794 More actions · Answer 2

Robert.Sterbal (11/21/2012)
I wish I could get the developers here to log some of the baseline data into the database. I often baseline information from tables that have large numbers rows and distinct rows of data in the datetime fields.

If you can get one of the clever ones to write a reusable audit/logging class that makes it easy for the rest to include the functionality you'll get better compliance with the plan.

They're probably already putting debugging output while building code; if there was a framework for multiple verbosity level debugging that gets logged then deployed code would have the verbosity set to minimum baseline-only capture. This system is even better if the verbosity can be escalated from within the database when you need/want to audit (or automatically escalated by an error handler)

rosej SSC Rookie Points: 48 More actions · Answer 3

What's the publish date for the other three articles in this series? The first one was very well written. Great topic as well.

Erin Stellato Ten Centuries Points: 1222 More actions · Answer 4

Thanks for the feedback 🙂 The second article should be published tomorrow (2012-11-27), I don't have a date for the remaining two yet, but will try to remember to post back when I do. Thanks for reading!

rosej (11/26/2012)
What's the publish date for the other three articles in this series? The first one was very well written. Great topic as well.

jswong05 Hall of Fame Points: 3553 More actions · Answer 5

Definitely. I agree with everything in this article. I am glad Erin writes this article as DBA best practice guide.

Alternatively, you could record troubled server by checking counters for CPU, memory, IO with system scheduled jobs while using triggers to record information for troubleshooting.

This is like when in trouble, patients automatic log symptoms, pains, temperature, color-picture and other diagnostic data to be used by doctors later. The principle works unless the server dropped dead. In that event, you will have the last black-box recorder data like before an airplane went down. That is why Oracle has DBA_History..... tables/views.

Jason

http://dbace.us

Jason
http://dbace.us
😛

Neha05 Default port Points: 1494 More actions · Answer 6

Neha05

Default port

Points: 1494

December 24, 2012 at 12:06 pm

#1571336

Nice article.

RudyPry SSC-Addicted Points: 404 More actions · Answer 7

Great job. very well explained. look forward to the series. 🙂

Erin Stellato Ten Centuries Points: 1222 More actions · Answer 8

rudypry (1/24/2013)
Great job. very well explained. look forward to the series. 🙂

Thanks for the comment! You can find all the baselines articles here: http://www.sqlservercentral.com/articles/baselines

Enjoy 🙂

Erin

Kafkaesque SSC-Addicted Points: 405 More actions · Answer 9

Can't wait to read the next instalment! This is precisely what I have been looking for.

arnipetursson SSCertifiable Points: 6557 More actions · Answer 10

Thanks for the article. Look forward to future installments.

Miles Neale SSChampion Points: 13147 More actions · Answer 11

I missed this when it first came out. Thanks, I can use it in parts of the job here. Very useful.

Not all gray hairs are Dinosaurs!