|
|
|
SSCommitted
      
Group: Moderators
Last Login: Monday, August 13, 2012 1:06 PM
Points: 1,928,
Visits: 224
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, February 22, 2011 9:03 AM
Points: 171,
Visits: 16
|
|
The item I will agree with you on is that Production DBA's can not exist in a vacuum. Prior to my taking over the production DBA group, the existing DBA's had a hostile attitude toward many of the developers which were really there customers. Given a good working relationship with the development division, your role becomes one more of consultant and less one of hated administrator. Of course you will still get to play bad guy from time to time, but don't start off thinking that it is your role to save humanity! Another item of note that in my environment development dba's have to work on specific work tasks due to billing rules. They can not float around and work on whatever is in trouble. Thus development DBAs here lead a rather focused existence based on whatever project(s) they are supporting. Many of the development DBAs have great experience but they are not NT Admins, just DBOs and limited SAs. My basic message is to manage your relationships with developers and their management. Given a good relationship your advice is more likely to be asked for and listened to!
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Monday, February 11, 2002 12:00 AM
Points: 24,
Visits: 1
|
|
Outstanding article and thought provoking issues. It's obvious from everyone's comments that the DBA field is evolving very rapidly. As an experienced MCSE (NT4.0 and W2K certified), but relative SQL newbie, trying to attain knowledge, excellence in performance and long-term security, where does one begin? Hands-on experience is a given. But, do you leverage experience with MCDBA certification? Followed by XML, VB, or a mastery of DTS? What are prospective employers looking for? Your thoughts?
Always Learn!
|
|
|
|
|
SSCertifiable
       
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
|
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:30 PM
Points: 31,436,
Visits: 13,751
|
|
|
|
|
|
Keeper of the Duck
Group: Moderators
Last Login: Today @ 1:13 PM
Points: 6,584,
Visits: 1,790
|
|
We just went through this cycle again.
Basically we chose experience and programming over the MCDBA. Had a candidate with the MCDBA, decent experience. No real programming background. He wasn't our first choice.
We brought on contract a different candidate with a good deal of mainframe programming experience and a bit more DBA experience. Certification credentials were less: only an MCP... having passed SQL Server 7.0 Admin.
The experience and programming were the deciding factors. Thus far we've not been disappointed in our choice. But I will say this, since we do a lot of Active Scripting and deal with a lot of VB developers, had a third candidate come along with heavy VB experience, he would have probably been chosen ahead of the guy we took. Fundamental understanding of MTS/COM+, ADO, and VB has been crucial to working on a problem app in my organization.
K. Brian Kelley bk@warpdrivedesign.org http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server Regular Columnist (Security), SQLServerCentral.com Author of Introduction to SQL Server: Basic Skills for Any SQL Server User | Professional Development blog | Technical Blog | LinkedIn | Twitter
|
|
|
|
|
SSCertifiable
       
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
|
|
I think it might do all programmers good to spend 6 months as a DBA...and vice versa. Brian, interesting hiring scenario - a great example that the days of calling yourself a DBA and everyone knowing what it meant are over - assuming all candidates have mastered the basics, in most cases I bet the one with a sub-specialty that matches the current tools/problem/etc gets hired. Far from the worst reason.
Steve, on your comment about XML - totally agree (one resolution shot already). If you're just serving XML there is not a lot to master on the db side. I think XML is great for some things, but as most of us do about new features, programmers fall into the trap of thinking it should be used for EVERYTHING. Will have to rant about this officially soon.
Andy
Andy SQLShare - Learn One New Thing Each Day SQLAndy - My Professional Blog Connect with me on LinkedIn Follow me on Twitter
|
|
|
|