Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

DBA Value Expand / Collapse
Author
Message
Posted Monday, November 10, 2008 6:44 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:10 PM
Points: 33,095, Visits: 15,202
Comments posted to this topic are about the item DBA Value






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #600328
Posted Tuesday, November 11, 2008 3:21 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 8:53 AM
Points: 1,049, Visits: 3,003
I think there is a hierarchy of requirements that stem from what a company sees as its fundamental needs for IT. As an example, a CEO may decide one of the company's aims is to know its customers better, and will see a CRM application as a means to get there. The IT department will see the app needs a database underneath it, and that both app and database need servers to sit on, and then that the servers will need a network OS to support them, and a network over which to communicate.

My experience has generally been that, whilst market forces fluctuate the cost of rare skills a little, the further someone's job is away from the company's fundamental stated need, the lower the level of remuneration. OK, it's a little simplistic, but a network, no matter how well designed, can never actually add value for the business; it can merely reduce costs. However, an application/database pair does have the ability to add value, so the company's much more ready to spend on people directly related to that pair. And if someone understands two or more of the necessary areas (e.g. a DBA who is also an acceptable programmer), the company will start spouting buzzwords like "synergy" and "integration", and will value that person all the more.

In short, how important a person is to a business doesn't determine how much they're paid so much as how well the decision makers in that business recognise why that person's job is important. Visibility, not utility.


Semper in excretia, sumus solum profundum variat
Post #600519
Posted Tuesday, November 11, 2008 6:01 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, July 17, 2014 7:55 AM
Points: 2,805, Visits: 3,067
Unfortunately most companies especially medium size companies do not think that way. They hire SQL developers and they are doing DBA duties which sometimes lead to disaster. However most companies just cannot afford to hire a full time DBA especially at this economic hard time. They want to hire someone that can do DBA work, SQL developers, .NET, C#......practically everything under the sun.
Post #600596
Posted Tuesday, November 11, 2008 6:24 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 7, 2012 9:23 AM
Points: 304, Visits: 716
"Visual Studio and development tools are different, and I know quite a few DBAs that are lost within those environments."

A DBA who does not know VS? That's a DBA? I oversee staff for four companies (part of our corporate org) and I have never hired any "DBA" who simply knows SQL Server. Our companies could not run, let alone stay in business with such staff.

To me, that is like a carpenter hiring a "hammer specialist". You build a house with a great deal more than just hammering nails - no matter how good you might be at hammer nails.

Maybe my thinking is this way because I came up in computing from the late 70's when you had to know it "all", and I must admit I am shocked at times these days when I interview or talk to young people who "specialize" in something so narrow that I am left wondering what these people do with the rest of their employment time. I have yet to see a DBA who truly needs 40 hours a week to monitor and maintain SQL Databases and operations - but maybe I am missing something - maybe our companies just run well because I have very talented people.

There are three DBAs that I oversee and I have incredible respect for each of them - they do a great job for us. But one of them is also one of the best VS/C#/VB.NET developers I have ever come across, and the other two are pretty good in the VS world as well.

I think this boils down (yet again) to the great unanswered question: What is a DBA? If that's a Database Administrator, well, how can you administrate a database without knowledge of the tools used to tap-in and utilize the very database you are supposed to be administrating?

Again, to me, that would be like hiring a general contractor to build you a house and then have the same guy pick up a hammer and ask "Hey, what is this thing?".



There's no such thing as dumb questions, only poorly thought-out answers...
Post #600609
Posted Tuesday, November 11, 2008 8:32 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:10 PM
Points: 33,095, Visits: 15,202
Blandry, I think it depends on what you're trying to achieve. I have development experience, but I'd be a low, intermediate developer at best in terms of coding skill and speed. However I understand how to put applications together and how to get data back they can use.

I'm also a strong administrator from the Windows side. I'm comfortable working in an AD environment and understand networking. That's incredibly valuable for troubleshooting and has saved me (and the company) a few times.

I'm not sure I think a DBA needs to be a great programmer. Unless you're asking them to check that code or watch out for CLR assemblies coming in.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #600700
Posted Tuesday, November 11, 2008 8:37 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, February 21, 2014 8:14 AM
Points: 194, Visits: 255
"I think this boils down (yet again) to the great unanswered question: What is a DBA? If that's a Database Administrator, well, how can you administrate a database without knowledge of the tools used to tap-in and utilize the very database you are supposed to be administrating?"

I whole-heartedly agree. I have seen DBA's that cannot develop and they have no idea how to help people optimize their code to take the best advantage of the platform they administrate. I would rather have someone who is a little more well-rounded (not necessarily in their mid-section).

Regards,
Joe
Post #600709
Posted Tuesday, November 11, 2008 8:44 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:10 PM
Points: 33,095, Visits: 15,202
Hey, I'm starting to resemble that remark.






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #600719
Posted Tuesday, November 11, 2008 8:56 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 8:57 AM
Points: 2,518, Visits: 3,718
I have never worked in an organization big enough where the DBA was only that. The DBA has had to to other things. The DBA is usually combined with the server admin. or programming roles; sometimes all three together.

The problem with this approach is that no one can be expert in all of them so one role suffers. It's very difficult to place a monetary value on the DBA role in the small shop environment. The value comes in the performance, consistency, and quality of the database.



Post #600731
Posted Tuesday, November 11, 2008 9:52 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Tuesday, May 13, 2014 5:10 PM
Points: 704, Visits: 258
Years (and jobs) ago, an interoffice joke circulated that was a list of IT Terminology. The only one I remember from it was the definition of "DBA":

"No one knows exactly what the DBA does but every company has to have one because they can't afford two."

Nuff said?
Post #600778
Posted Tuesday, November 11, 2008 10:07 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 7:58 AM
Points: 1,549, Visits: 1,890
I think a good part of the premium that is applied to a DBA's salary versus a developer is that the DBA is also an insurance policy againt data loss. If a disaster strikes, you may call in some developers to help bring things online but the DBA is going to have to ensure all the data is in place.
Post #600790
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse