asked
Want to become a SQL DBA
Hi my name is Ram....Now i am working as a GIS Engineer in one CMMI Level 5 company....Now i want to become SQL DATABASE ADMINISTRATOR...Am i elegible to DBA?, Please clarify..Thanks is advance... Thanks is advance...
To be able to become a DBA, you need to learn how to write questions at the right place, not in the title. :) Sorry, I couldn't help it, I just had to joke with you.
Can you tell us a bit more about yourself. How often do you interact with SQL Server? Do you currently write TSQL today or support any MSSQL databases? How long have you been working with MSSQL if so. If you have zero expereince then you have a bit of a rough road ahead of you but that shouldn't stop you from following your dream to become a DBA. Go out to CDW and purchase a copy of developer edition then download adventworks and get started. There are numerous resources out there to help. Us here being one of them. For someone just started out I like to recommend Pinal Dave's "Joes to Pro's" series. They are not to expensive and really helps to build a strong foundation.
Yes i have good experience in DBA...But my doubt is, My experience(3+ years) and designation (GIS Engineer)is considered or not? If consider how can i put in resume?
Qualified as an entry level DBA, sure (but almost anyone can do entry level, I've taught English majors before). Qualified as something more? Based on what you've provided, no, I can't say that you are. If you were applying to me for a job, even as entry level, I'm going to want to understand how much TSQL you know, if you've used SQL Server (or Oracle, or MySQL, or Sybase, or Access...) and what you've done with it. Simply saying GIS suggests to me that you've worked on the helpdesk or you do system configurations or something like that. It doesn't tell me that you've done anything with databases which means if the guy sitting next to you knows how to write a SELECT statement and shows me, he's more likely to get the job than you are. If you've done SQL Server work, you need to bring that out. If you haven't, in order to be better qualified to be a DBA, that's where you need to get started.
Yes..I already got SQL Database administrator job in another good company..I havebeen working for last 4months as successful...But this job is contract of 6 months...After that can i use these both experience(3+ years as GIS Engineer) and (6 months as SQL DBA)???
Sounds like you are on a pretty good path. Yes indeed you should list both the GIS and the SQL experience. You should also check out [SQL PASS](
http://www.sqlpass.org) for links to virtual and physical events where you can network with other SQL Professionals. Hang out for a bit on this board and try to answer some questions. There are tons of bloggers out there writing about every topic imaginable with SQL Server. Your key will be to learn all the basics and to learn TSQL well. @Grant Fritchey has written a number of books on the subject. One would be wise to visit Amazon and pick up a few on TSQL and Execution Plans.
yeah, there's no reason you can't list both. In fact, you should list both. More experience is not bad, but you need to be really clear what you know, what you have done, so that it's everyone can tell. Again, just based on what you've said, I'm still leaning towards Jr. DBA, entry-level because you're not making it clear to me that you really know the job. There are not many entry level openings out there that I'm aware of.
Eligible is a very subjective term. For me a DBA has to be someone who loves the nuts and bolts of how things work. They have to come with a strong work ethic and clearly be Client focused. A DBA takes responsibility for the data they manage and take it personally when there are issues. They are proactive and prepared. A DBA also knows how to secure and optimize while guaranteeing up-time and accessibility. I guess it depends what you mean when you say "Am i elegible to DBA?" Listing database experience is a start. And defining what you assume a DBA is, as the term means different things to different people.
I have hired a number of DBA's of all levels. When I am looking at hiring a Jr. level DBA I have to tell you that I assume nothing. I assume you don't know how to install, configure, backup or restore a database. But I do expect that you know these things within the first couple weeks of working for me. If you know how to do these things that I think you are well on your way. I mention that because I figure I am going to get some odd looks from the next statement. When I hire a Jr. DBA I look for attitude, personality, and the desire. How would you fit into my team, do you have a good attitude when it comes to learning new things, and are you willing to do the work. See a Jr. DBA in my mind is someone who doesn't have a solid base to start from. So I want to do all I can to help them get to that base. Every job is different, every hiring manager is different. So may want you to have different skills. When it comes to me and my opinon I want to know a Jr. is going to go home after work and continue to refine the skills they have learned. They are going to be at User Group meetings, they are going to go to SQL Saturdays. With that being said... I have to turn the question back to you. Do you have what it takes to be a Jr. DBA. And more importantly, do you have what it takes to be a mid level DBA. Are you going to put into it what is needed to move on to the next step? If you just want a job, then I don't think that a DBA is the place you want to be. I think being a DBA is a Passion.
Thanks for the comments on both the answer and the event this weekend. The event was awesome from where I was seated, but there are always things that I would like to improve. @TRAD - When you mentioned people with 3-5 years, I almost jumped up to scream Amen. I know just what you are saying. @Grant - I am with ya, just because the know a ton, doesn't mean there is room for them on my team. I like this Q&A here. I did not know this was here.
What is sad Chris is many DBA's I interview with 3 to 5 years experience can't explain the difference between clustered and non clustered indexes, they can't name 3 system databases, state they are an expert at tuning SQL on 2005/2008 but can't rattle off a single DMV. I take nothing for granted when looking at a resume either. I too look more at attitude and personality when interviewing Jr DBA's as well. If they are a good fit with the team, I can teach them everything else. It is the cocky DBA's that I run from. :) Congrats on an awesome event this past weekend. The twitter feed was awesome. Everyone seemed to the enjoy the snow too.
No odd look from me. Attitude, personality and desire should be a big part of hiring anyone at any level. Same thing goes with how you fit on the team. I know people who could DBA rings around me that I wouldn't want to hire because they're personally unsavory. I know others who are clearly not up to snuff technically, but are hungry enough and team players so I'd hire them in a heartbeat. I think you're largely on track. Also, great job this weekend. It was an amazing event.
I think there may be some orginizational differences here. In the orgainizations I have worked for as a DBA, a DBA, even a junior one, was expected to know a fair bit about SQL and was given SA access on several servers, if not all of them, very quickly. DBA's were responsible for keeping the SQL Server instances running, amoungst many other things, and a major mistake by the DBA could shut down whole departments until it was corrected. So, they expected their DBAs to come with experience in SQL, and a track record of being reliable and able to handle responsibility. On the other hand, those organizations would happily hire someone with a touch of computer experience and the right attitude as a Jr. SQL Developer. I have trained a theater-major whose only programming experience before was basic HTML and she did quite well. In looking at Jr. Developers, I care far more about attitude than skill. As Blackhawk-17 said, DBA means different things in different organizations.
Same was the case in the organizations I have worked for. A novice could have been hired as a Jr. SQL Developer but not as a Jr. SQL DBA.
