More Tips for New (and old) DBAs

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Craig Outcalt » More Tips for New (and old) DBAs

32 posts, Page 4 of 4

«««1 2 3 4

More Tips for New (and old) DBAs

Rate Topic

Display Mode

Topic Options

Author

Message

SQLBOT

Posted Monday, June 06, 2011 7:35 AM

SSChasing Mays

Group: General Forum Members
Last Login: Monday, February 18, 2013 3:22 PM
Points: 626, Visits: 835

Lee Sloan (6/3/2011)

... what I'm effectively asking for is suggestions of how we significantly improve this, rather than band-aid it.

I think it comes down to management recognizing issues within their staff and working to address them through training or correction.

Many people don't like the idea, but metrics are a way to improve it.
If person X closes 150 tickets per month and person Y closes 10, it gives management something to work from other than an anecdotal feeling or a group consensus. I understand (all too well) that not all tickets are created equal, so my oversimplification needs to harness some other value matrix that makes sense for your company.

Deriving continuous improvement through measurement is the "next step" in the capability maturity model that many/most places never reach.

~Craig

Craig Outcalt

Tips for new DBAs: http://www.sqlservercentral.com/articles/Career/64632
My other articles: http://www.sqlservercentral.com/Authors/Articles/Craig_Outcalt/560258

Post #1120262

dbychen

Posted Monday, June 06, 2011 9:00 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, February 13, 2013 2:32 PM
Points: 135, Visits: 459

This is a great article pointing some important areas leading to team work spirit within a DBA team and providing superior professional services to an organization for a DBA team.

A DBA team needs to establish proven and consistent procedures to perform support. The purposes for these are to inform the involved parties for a database change to take place, to obtain required responsible parties' approval for a change, and finally to ensure a change to be well integrated into the current application.

Any DBA team members who can solve tough architectural and technical problems are certainly great asset for a DBA team. However, heroes building up with "short-cuts", "back-door" practices, and the like are certainly leaving changes without necessary tracking, undesirable for applications of established organizations, and away from team spirits as well.

Thanks Craig for your nice article!

Post #1120319

« Prev Topic | Next Topic »

32 posts, Page 4 of 4

«««1 2 3 4

Permissions