Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


On-Call Duties


On-Call Duties

Author
Message
tjaybelt
tjaybelt
SSChasing Mays
SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)

Group: General Forum Members
Points: 633 Visits: 470
Comments posted to this topic are about the item On-Call Duties



John.Sansom
John.Sansom
Mr or Mrs. 500
Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)Mr or Mrs. 500 (513 reputation)

Group: General Forum Members
Points: 513 Visits: 1558
An excellent article and thank you for sharing it with us.

It would be great if you could also make available the Excel document that you describe.

Cheers,


John Sansom (@sqlBrit) | www.johnsansom.com
SequelDBA
SequelDBA
SSC Rookie
SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)

Group: General Forum Members
Points: 48 Visits: 1057
Excellent article...Thanks


KU
BJ Hermsen
BJ Hermsen
Mr or Mrs. 500
Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)

Group: General Forum Members
Points: 507 Visits: 880
I would suggest taking it another step. It may require some dreaded overtime to get in place but is well worth it. We are dba's not secretaries or monkeys.

Automate it. Then the data can be stored into a repository automatically and you can use ssrs or excell or whatever to view your trends and histories.
tjaybelt
tjaybelt
SSChasing Mays
SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)

Group: General Forum Members
Points: 633 Visits: 470
Robert Hermsen (10/27/2008)
I would suggest taking it another step. It may require some dreaded overtime to get in place but is well worth it. We are dba's not secretaries or monkeys.

Automate it. Then the data can be stored into a repository automatically and you can use ssrs or excell or whatever to view your trends and histories.


i agree. I love to automate things, and this is one that dreadfully needs it.
thanks for the comment and reminder to us all to automate.



salman.samad
salman.samad
SSC-Addicted
SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)SSC-Addicted (465 reputation)

Group: General Forum Members
Points: 465 Visits: 230
Excellent article and particularly the point related to Checking on the Backups.

A lot of times DBAs or System Admins fail to check on the backup status only to find out they have to restore at a point way back in time which leads to unnecessary inconveniences at all levels of an organization.

The only point I would like to add is that a DBA should not only check for successful backups but also periodically perform a restore using a backup set in order to ensure that the backups are indeed intact - furthermore this also helps being compliant when it's time for the company's audit!
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: Administrators
Points: 42278 Visits: 18876
To me these are things that are daily checks, things you need to make sure are available if you get called when you're on-call. Issues should be documented and also raised as some sort of turnover for the next person to be aware of.

My goal has always been to automate these things, but also to proactively manage the systems, looking to catch things before they fail so that you're not getting called!

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
tjaybelt
tjaybelt
SSChasing Mays
SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)

Group: General Forum Members
Points: 633 Visits: 470
Steve Jones - Editor (10/27/2008)
To me these are things that are daily checks, things you need to make sure are available if you get called when you're on-call. Issues should be documented and also raised as some sort of turnover for the next person to be aware of.

My goal has always been to automate these things, but also to proactively manage the systems, looking to catch things before they fail so that you're not getting called!


I can see automating some of the items i have detailed. But you are correct, some manual intervention still needs too occur, to ensure that your systems are in proper working order.
Something that can gather and store the historical data would be nice. Automating some of the data gathering would be nice. But having a human DBA look at it, still seems like a necessity.

Another DBA here just went on call this week, and thought to grab snapshots with SQL Compare as part of his on0call duties. Nice addition. If something goes wonky during the week, we have a snapshot to compare with...



Regan Galbraith
Regan Galbraith
SSC-Enthusiastic
SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)SSC-Enthusiastic (149 reputation)

Group: General Forum Members
Points: 149 Visits: 265
tjaybelt (10/27/2008)
Steve Jones - Editor (10/27/2008)
To me these are things that are daily checks, things you need to make sure are available if you get called when you're on-call. Issues should be documented and also raised as some sort of turnover for the next person to be aware of.

My goal has always been to automate these things, but also to proactively manage the systems, looking to catch things before they fail so that you're not getting called!


I can see automating some of the items i have detailed. But you are correct, some manual intervention still needs too occur, to ensure that your systems are in proper working order.
Something that can gather and store the historical data would be nice. Automating some of the data gathering would be nice. But having a human DBA look at it, still seems like a necessity.

Another DBA here just went on call this week, and thought to grab snapshots with SQL Compare as part of his on0call duties. Nice addition. If something goes wonky during the week, we have a snapshot to compare with...



On the same vein of automating, one useful tool is an automated restore of your backups on another server.

That assumes you have another server(s) available - in our case we have a customer log-shipping of LitetSpeed backups to off-site DR servers. This is configured to keep those off-site DB servers 1 hour behind the live servers (which CAN be invaluable when a junior DBA says ... "oooops!!" when asked to do an update). In conjunction with MOM reporting set to alert (via SMS and E-mail) on failures, we have automated, alerting knwoeldge of the viability of our backups.

Needless to say, several of the other obviously automatable tasks (like the space available etc.) are also configured to send MOM alerts on threshold values (typically at 80%, 90 %, 95% and 99% full - so no server should run out of space without at least 4 alerts).

This does add an additional check on the "daily checks" list however - make sure MOM is up and working BigGrin
BJ Hermsen
BJ Hermsen
Mr or Mrs. 500
Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)Mr or Mrs. 500 (507 reputation)

Group: General Forum Members
Points: 507 Visits: 880
a benefit to storing the data is that in lieu of alerting on 80-90 % drive utilization you can alert on % changed. It allows you to catch when suddenly your drive with 3% monthly growth suddenly changes to 15 % quickly shortening your window.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search