December 9, 2004 at 1:28 pm
Does anyone have any tips on landing that first SQL Admin position? It gets frustrating looking for positions that all require 3+ years of experience but I can't gain the experience without getting a position. I have never seen a Jr Admin position before. Please advise
Thanks
James
December 9, 2004 at 6:49 pm
Quite honestly you are probably going to find a developement job easier and from their can get the expeirence and chance to do Admin work. Once you get in then assert yourself as a knowledgable person and put forth the ideas you have of making SQL Server serve the company better, as you do this then you get noticed and get the experience a good Admin really should know and that is good devleopement skills. I have run into to many Admins who don't know anything about the code I am implementing they jsut create logins, provide access and do backups. Nothing more.
December 10, 2004 at 4:31 am
I agree completely, I've been a SQL DBA for the last 8 years and started at the bottom. There are many routes into the profession but the best one is to start as a developer and work up. Dont try for the Paper MCSE or MCDBA, that's possibly the easiest but in order to do the job properly you'll need the experience you'll aquire and that cant be learnt from books/cramming.
I encounter a lot of people now that think because SQL has a nice GUI that it's easier than it used to be to administer, i would counter that by saying yes it is easier to do some of the jobs with the gui but to do things properly you need to know how it works under the hood (sort of like a driver thinking he's a mechanic because he can drive).
All I can say is that being a DBA is an exteremly rewarding (and often incredibly frustrating) career choice and that I love it.
Good luck
December 10, 2004 at 6:52 am
I also started as a developer, albeit as one who had a knack for designing databases from using Access. Eventually my knowledge of SQL grew, and I become the de facto DBA. And then one day they made me a DBA. The time prior to being a DBA gave me the experience necessary, and the time as a developer is still invaluable in helping other developers get what they need from the database.
December 10, 2004 at 9:38 am
Yup, start out as a developer, and branch out from there. Do your homework and such on databases on your own and start volunteering for stuff database-related. It'll probably take a while, but eventually, someone will see you have enough database experience on your resume sooner or later and you'll get the job you want.
December 10, 2004 at 9:47 am
I started as Systems Administrator in small company and I was the only IT specialist there. We had database servers and it was good experience as for junior DBA.
December 13, 2004 at 1:49 pm
The reality is that very, very many places will hire solely on the basis of paper certifications. Yeah, experience is great, but if you want the quick way in, get those certs and puff up the resume with them. Trust me.
I wish they'd been around when I was starting out 25 years ago, it was a very, very tough road with no exp. and no degree...
(And no, I personally wouldn't hire on the basis of certs and I studiously avoid getting them for the fundamental reason that there is no corelation between competence and certifications.)
December 16, 2004 at 11:05 am
The advantage of getting the certs is that you demonstrate a willingness to learn everything and anything you need to learn for the job. I agree with John, I wouldn't hire based on the certs, but it does tell me something about the character of the applicant. Besides, you come away with a lot of valuable information about the theory behind what you are doing, rather than just knowing how to do it.
Starting as a developer is probably the best way to get where you want to go. It will also help you understand WHY people want to do something a particular way and, in many cases, will give you the basis for persuading them to do it the RIGHT way.
Good luck.
Don
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply