DBA vs Database Developer
-
I have 5 years SQL Server experiences, plus working with Oracle database for 5 years. I did data base design, writing SQL, stored procedures, trigger, function, DTS Packages .... For SQL Server I also do some DBA works eg granting permission, backup database...
I have a question, is a Database Developer more variable than a DBA according to the industry or vice versa?
Comparing to a DBA with more than 10 experience and a DBA with less than 5 years experiences, where do I stand?
-
"I have a question, is a Database Developer more variable than a DBA according to the industry or vice versa?"
A DBA has the following major topics as his/her daily tasks:
1. Security 2. Performance 3. DB Availability
But I would say a DBA with strong devloper experience is always welcomed and vice versa.
-
I think it really depends on the job you're applying for, or the position you're comparing your experience to...
I would think database developer deals with the front-end programmers and helps with app. architecture, etc.
The DBA IMO, would be managing the production databases as mentioned above.
I would play up the experience that is requested, as there is a certain bit of overlap.
-
".... For SQL Server I also do some DBA works eg granting permission, backup database..."
Yeah, but can you dance?
All the tiltles are silly. Bottom line is how much you're making and do you like your job.
Or in English: Apply for either job, but when interviewing, you need to ask the questions to find out what you're going to be called upon to do, and you need to decide if you want to do that and what it's worth.
How about "Abstract Reality Engineer"? "Information Integration Specialist?" Oh, I know: "Information and Data Integrating Organizational Technician" <-- Yep, that's what I am.
-
The 90's dot com startups had some hilarious ones...
-
John, I can dance too. You want to take me out!!!!!!
My company is big on .Net and C# right now. Even though I am good at database, my manager said he could not give me a promotion unless I know C#.
Recently I found out they hired a guy with C# experience and treated him liked a king. On the other hand I worked 60 hours a week and meet every single deadline even they are ridulous. My senior management still not happy because I don't know C#.
Sometimes I wonder if I keep on working as database developer/DBA, what kind of future do I have?
-
There have been various debates on these forums in the past regarding dba's that stay strictly on databases or 'spread out' and the answer is always the same: it depends.
C# is not that hard. If you've been driven enough that you are a dba or database developer, you can learn C#.
Some folks don't like change, especially in the workplace. Well IMO, IT is not the career for them. This stuff changes all the time and will continue to change all the time.
So your employer is really excited about C#? The question on my mind is why. Are they short on developers? Did your bosses boss go to a conference or read a web article on how C# is the next best thing? Are the current developers dragging their feet on C# or .Net in general?
I think you're in a pretty sweet spot if your boss is urging you to learn something new, he/she may be more likely to fund some training. At least you're not working at one of those places that is completely stagnant, still using outdated software...
-Don
-
I've been doing both DBA and development work in SQL since MS-SQL 4.2. When I started that I was also learning ASP (interdev 1.0). I still do web development (learning .NET, C#, VB.NET) and SQL application development and am the SQL DBA for our group. BOY is there overlap...
My point is that each teaches you things about the other. Things you learn wearing the DBA hat in regard to security and performance, for example, help you write better applications. And problems with applications help you learn more about DBA.
IMHO the person with the broader experience has more to offer. That does not necessarily make you more viable in the marketplace but it MIGHT make you happier in your job.
------------
Buy the ticket, take the ride. -- Hunter S. Thompson -
Yeah, I agree with that last post...
Being proficient / knowledgable about both FE's and BE's has made it much easier to discuss things with developers on either side.
Knowing how your side of the app will work with the other side helps in so many ways...
-
I especially like G Bryant McClellan's point that "each teaches you things about the other.", I cannot overstate the importance of this point.
-
I think it's much harder to get respect as a database architect/developer just because other people don't understand the nuances of what we do. Too many people have created a simple db in Access, so they think that's all there is to database development. I tell them the simple stuff is very simple but the hard stuff is very hard -- but they don't believe me.
-
If they only tried it once they'd probabely get it
-
As soon as you re-write a query they've written so that it runs in two seconds instead of three hours, getting the respect is no problem
--
Adam Machanic
whoisactive -
Remi - for once I have to disagree with you (:-(
I know HEAPS of people who have been developing databases for YEARS - who don't even follow the very basics of naming conventions, choosing the datatypes with care etc.. leave alone using indexes discriminately or even normalizing to some degree...you should see some of the clunky databases out there - it's SCARY & it'd want to make you curl up and die....
**ASCII stupid question, get a stupid ANSI !!!** -
I see your point. I'm working with a nightmare database here. I'd have to complete my point with another step : correcting all there mistake in there face. Maybe they'd get the point then
.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply