December 19, 2007 at 6:55 pm
I am a SQL Server developer and moonlighting as a DBA. I know how to backup, restore, create user, create user permission, create linked server, start and stop a server, look at error log to figure problem, run Profiler, fix transaction log if too full, find out whose transaction using up all the CPU and kill that jerk, find out which transaction caused the tempdb full...ok I am kind of a application DBA (Part time).
Since I am out of a job, I apply every job having SQL Server as the buss word. I must be crazy or I am very desperate. I applied for a DBA position. I did not even look at the job carefully. The company actually called me up for an interview even my resume was indicated I was a developer.
I am scared, I don't know how to do log shipping, failure clustering and all kinds of good stuffs a DBA does. I don't even know what a DBA does. The job description said to develop process to ensure high availability and recoverability of databases, collecting and analyzing data for capacity planning and performance monitoring.
I never care about those things.
Anyway I probably will not get the job!!!!!!!!!
:sick::crying:
December 19, 2007 at 8:29 pm
Have a look at http://www.sql-server-performance.com. You should be able to get some good info about capacity planning etc
December 19, 2007 at 10:05 pm
Refer BOL for Log Shipping and Clustering
December 19, 2007 at 10:35 pm
... and don't panic... hit the books on those areas that you're light in... remind the future employer that your resume said "developer" and that you've got some boning up to do to be a full fledged DBA...
...another thing to remember is that you might be the best thing they've seen or will see... don't be afraid to sell your learning abilities... just don't lie about what you know. The truth always works the best and I wouldn't be surprised if you got the job.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 10:48 pm
Jeff is spot on with his recommendation about telling them the truth and highlighting your learning abilities (and contacting this forum is part of that) - it really is a refreshing to hear the truth. When I applied for a position with my current employer, a told them exactly what I knew (which was the relational database engine only), got the job and now, I am regularly developing SQL, Analysis Services, SSIS, Reporting Services and am about to be developing using Performance Point. My employer did believe me and still has faith in my abilities.
Good luck with your application
December 20, 2007 at 6:32 am
I agree with Jeff and highlight what you know, don't sweat what you don't. Show them you can learn and are willing to tackle any project. Show experiences from your past that demonstrate this.
And good luck!
December 20, 2007 at 7:24 am
Best of luck.
Just remember, you don't have to be the best DBA in the world, just the best DBA in the room. If you know stuff and no one else does, that makes you the expert, however light your knowledge may be. If you land the job, I'd recommend reading Craig Mullins book "Data Administration: The Complete Guide to Practices and Procedures." It's a general work that doesn't drill down on technology, but talks about responsibilities and processes and best practices that are generally applicable to the DBA job. It'll help.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 20, 2007 at 8:15 am
I'm so glad that you've got an interview! :w00t:
Remember to concentrate on what you can do, highlight what you have done in previous similar roles, and point out occasions where you've had to pick up the reigns and learn new skills in short periods of time.
You know you can do this job, they obviously think that you can do this job; show them that you can. Personal traits can overcome deficiencies in skills, having worked in many different environments shows how adaptable you can be.
Good luck with it, and let us know how you get on!
December 20, 2007 at 9:46 am
Whatever you do, don't lie to them. If you get asked a question on an area you're not familiar with, tell them that you're not that familiar with it. If you try to bluff based on some quick reading you may get caught out, especially if the interviewer knows the area well.
Personally I'd prefer honesty over knowledge in a candidate. Knowledge can be taught.
And congrats on the interview.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 21, 2007 at 2:18 am
Well done Loner! Good luck on the day - and let us know how you get on!
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
December 21, 2007 at 2:41 am
Hi,
I was scared too about applying on DBA job even I am software developer and worked several years with C++. I was prepared for this kind of interviews by learning and reading a lot of SQL server stuff, even on this site which is the most wonderful sql stuff site. From 5 interviews I had only one where I cannot faced but honorable because of complex tehnical interview (Informix database like). 2 of interviews were a succesful for me. One of them they told me finnaly that I am overskilled so it was my decision if I want to come join with them. I accepted cause of their good offer. So, now I am a DBA and proud to reach my dream. However, they hired me as software developer but my job duty is one of DBA. They want to help them as software developer too. ๐
December 26, 2007 at 7:25 am
Hi Loner, congratulations on the interview, I hope all went well and an offer for the follow-up interview is on it's way and that it will lead to an offer. There are no easy answers for interviews, each is unique, two people meeting for the first time. Think of what you respect and expect if you were interviewing someone, the person on the other side of the table. A good match for the team or department is the most important, then technical skills. There is no use in having the most knowledgeable person if they disrupt or can't work with the team. Take a deep breath and go for it!
December 26, 2007 at 11:54 am
Many companies have too loose definitions for DBA role. I've been on some interviews where all they wanted from a "DBA" is to write stored procedures and stuff like that. If you feel as strong developer you don't have to worry about.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply