Wearing Hats


  • Wearing Hats

    I saw this debate and the referenced article on engineers working harder for their salary and it got me thinking. After all, in the IT area, I've always been used to doing more than one job, usually at smaller companies where there are less people to handle all the jobs that need to be done.

    And in the cases where we've had enough people, I've usually looked for other work just to break up the DBA duties. Usually in some type of development to be more creative and work at implementing some feature. So this week's poll is:

    Are you more than a DBA right now?

    Do you do more than just DBA work? Is it expected? Is it in your job description? Or did it evolve that way?

    I certainly do more jobs, especially since I'm responsible for all the SQLServerCentral.com servers. I get to play Windows admin, mail postmaster, and various other jobs as well as DBA. It's interesting and it keeps me busy and learning about new technologies, though it can be frustrating when I just want something in Windows or mail to just work as advertised.

    I don't think I'll ever get to be "just a DBA" anymore, especially with SQL Server 2005 and all the programming capabilities. My VB and C# skills probably need brushing up at this point.

    Steve Jones

  • I am a SQL Server / Data Warehouse developer, doing data modeling, design and writing codes. However we do not have a DBA so I am the 'DBA' too.   Actually I don't mind, it is fun doing different things.  Luckily I don't have to be on-call.

  • My formal title is Systems Support Analyst.  I deal with a big umbrella though - from helpdesk support (printers malfunctioning, new scanner install, software not working properly) to DBA (ERP system, HR/Accounting systems, in-house systems) to programmer to report writer and designer.   No two days are alike because of all the hats I wear, and that's not necessarily a bad thing.

  • Although my title is 'database analyst', I spend a decent portion of my time as a VB developer and general IT lackey as well.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • I started as a programmer/analyst and evolved into the DBA role.  My official titile is now Senior Systems Analyst but it could very easily be Sr. Systems Analyst/DBA/Sr. Programmer Analyst/Networking Engineer/System Administrator/Application Super User.

    I enjoy all the different things on my plate as no day is the same as any other day.  It does get frustrating when searching for a different job since an employer would like to see your title matching the skills they are looking for.  It also holds me back from being a complete expert on anything specific.  I end up having to know a lot about everything which tends to make some of the expertice lacking due to time splits between all the other duties.

  • I am in a similar situation as Jeff.

    I started way back as what was then called a "programmer", and I now find myself as the only one left from a team of developers, having inherited a couple of VB6 applications and associated databases. I maintain the databases, monitor and patch the servers they run on, maintain the applications and a couple of modest websites, lots of ETL and reporting queries, and an assortment of vbs and command-line scripts.

    I would like to move on but am not enough of a specialist to do any of the jobs I see advertised. I sometimes wonder if this kind of situation is an occupational hazard for database developers.

  • I wear many hats as well.  But as with any company, at least with any one that will survive, adaption is key.  Before my addition to our team, for example there were from time to time deployments that failed because of problems intergrating our eq within networks, and just a it's never been done before sort of situation.  But since my addtion to the team I can say we have had  100% success from an IT intergration perspective.  An example of a solution I was key to impliment was to reprogram one of our machines from one core and pretty much change it into another model thereby dealing with a NT4 to xp client driver related security issue.  Boy did I ever get a nice stapler for that one. 

    My official title is Information Systems Architect, and with that I'm responsible for the rolling out, supporting Servers (SQL Exchange etc), clients, software that sit on top of those systems.  From workflow control processes to custom accounting apps, internal or external ones, end up under my belt.  Also, fundimental services such as email admin, professional graphic related client issues, web admin, driver support and level 3+ tech support. As were in the business systems and services business I do enjoy a broad spectrum of challenges from every area whether 'ix to MS sites.

    I'm well studied, trained, educated in most IT deployments, so incredibly rarely find snags that can not be over come with diligence.

    I'm currently managing and migrating our core business process over to .NET and 2k5.  From jumping from VB6  over to asp and then back to .Net I've found myself coming full circle.   It an exciting time where I'm growing again getting a chance to you some of the training I've built up with the new MS toolset.

  • My post is called IT Project Manager, which in fact means, that I'm DBA, user support for the software running on SQLS (information system), report generator, and several other things... I cooperate with the software manufacturer on further development (filtering and translating requirements of our users into language the analysts and developers understand, and translating their replies back into language our users can understand); sometimes I have to find the optimal solution myself, because we have the largest database of all clients and the developers sometimes fail to optimize their SQL for such environment.

    Very interesting work, especially because there are so many different things to know (and to learn).

  • Hell yes, I wear lots of hats (this morning working on a script engine failure in IIS) and in the overall it's not a bad thing (though sometimes overwhelming). Flexibility is a valuable job skill, and keeps one alert.

     

    [and it's not just my employer... my wife is seriously considering buying an established website that is largely PHP ... arghhh guess who's gonna wind up learning new things!!]

     

     

    ...

    -- FORTRAN manual for Xerox Computers --

  • I'm a Marketing Manager who's also responsible for administrating my department's Marketing Datamart.  I've been writing SQL code (in a marketing capacity) for over 12 years.

    I'm also responsible for managing a team of 10 persons responsible for executing every retail, direct mail and other promotion produced at my company.

    The datamart is the heart and soul of the department and housing it on SQL Server platform allows us to do much more with fewer persons than most companies our size.

  • I started as a bull mainframe operator and now am a sql DBA, windows sysadmin, Solaris sysadmin, ingres DBA, AIX sysadmin and dabble a bit with Oracle, IIS, SAP, "And any other relevant duties"  Never a dull moment here.


    TTFN

  • Actually I do too more than just DBA jobs. I think wearing a lot of hats is good in some sense but it prevents you from being an expert on a particular subject. What do you think?

    Cheers,

    Zubeyir.

  • I've always done more than just DBA.  At my last job, I was there for 11 years, I was the Software Development Manager, I did application as well as database design and was one of the top developers.  I recently changed job o a company where initally they wanted someone with all those skills, but now they thinks it's overkill.  So if anyonw is looking for anybody ... give me a buzz.

    Personally, I think we as DBA should have a wide range of skills, It makes you more valuable and will mke your job easier.




    Curtis Smith
    SQL Server DBA
    Well in worked in Theory ...

Viewing 13 posts - 1 through 12 (of 12 total)

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