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

Accidental DBA Expand / Collapse
Posted Friday, April 27, 2012 9:57 AM


Group: General Forum Members
Last Login: Thursday, September 11, 2014 10:39 AM
Points: 2,803, Visits: 3,068
For the last 4 companies I worked for, none of them had a 'real' DBA since they all thought SQL Server was just an easy database to maintain. So I am the database developer becoming an 'accidental' DBA, doing backup and restore, maintaining user security, creating database, tables and so on.
Now when I look for job, the company that is looking for a database developer saying that I am too much of a DBA, the company that is looking for a DBA saying that I am too much of a developer.

My career seems to be doomed!!!
Does anyone have this problem or just me?
Post #1291678
Posted Friday, April 27, 2012 10:05 AM



Group: General Forum Members
Last Login: Yesterday @ 7:58 PM
Points: 20,705, Visits: 32,356
I'm not an accidental DBA, I got into this because I wanted to and found it fun.

You are what I consider a Hybrid DBA, you have experience on both sides of the fence, as do I. The key is to highlight how this makes you better on either side of the fence. Depending on which side you are applying (DBA or Developer), you have to demonstrate how you can apply that other knowledge to the benefit of the company.

Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1291686
Posted Friday, April 27, 2012 12:52 PM



Group: General Forum Members
Last Login: Yesterday @ 1:46 PM
Points: 5,384, Visits: 7,458
I have a similar problem, partially because I'm a contractor who does whatever comes along, partially because I've never dedicated in one direction or the other.

I keep two resumes. Well, six actually, but for this discussion two is appropriate, as the rest is mostly formatting. One is development heavy and the other is administration heavy. This is perfectly legal, since neither lies about what I've done, I just omit different duties that don't lend themselves towards the job I'm looking to interview for.

When they ask you about the administrative duties, answer their question then steer the conversation back towards positions where you were more heavily involved in development.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Post #1291758
Posted Friday, April 27, 2012 1:01 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, February 18, 2013 6:53 AM
Points: 60, Visits: 122
I am also having two different resume for developer and administrator. When I am trying for development post I give emphasize on development duties but I also keep some of basics of administration which gives me advantage of multiple skill sets.
Post #1291769
Posted Thursday, July 19, 2012 1:43 PM



Group: General Forum Members
Last Login: Monday, September 29, 2014 6:31 AM
Points: 24, Visits: 107
The multiple versions of your resume is a great way to go. However I have a suggestion for the interview itself. If you are applying for a developer position, do not hide your DBA skills. Point out that you do understand how SQL Server works and are less likely to write poorly written procedures. (The type of code that make us DBAs pull our hair out looking at bad code wondering why the developer did THAT!)

Likewise, when going for a DBA position point out your strength in working with T-SQL. Your skills that will help you understand someone else' code and offer better suggestions back to the developers for optimizing code, suggesting better use of indexes, ...etc.

Point out your strengths for the position in question, but also play up how your other skills will help with that position.

(What color is your database?)
Post #1332526
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse