There are three camps of people I’ve met when it comes to discussing certificates in IT.
- Oh, that’s nice to have, but I’m indifferent otherwise. (95% of the people.)
- Oh, you are certified?! That’s amazing! I need to talk to you all about that! (3% of the people.)
- Oh… you are certified? So you’re one of those paper DBA’s huh? (Cue them throwing your resume in the trash.) (2% of the people.)
Certs can have a bad rap because there are many certs that you can achieve that hold little weight. Like when you complete a couple hour video training course that you pretty much need to just click through and at the end, you can pay money to have them issue you a cert.
You can also cheat on the exams, I’m not sure how exactly since exams that hold weight have a fairly rigorous process. For my exams; I needed to remove all accessories, show my electronics are turned off, display several forms of ID, receive a quick visual patdown, pictures are taken of me, I’m verified by multiple people on my way to the test, and I’m recorded in a small isolated room the entire exam.
There are people who post answers or try to memorize the exam from braindumps, which is also against the rules of the exam. And there are also people who go through boot camps or cram as much as they can from a single study book over the course of a month and then take the exam. The last option is better but still not great. At the very best, it makes you a paper DBA.
Paper DBA – A person who holds a lot of knowledge about the product without the actual experience to apply what has been learned to real world scenarios.
Ok, that’s a lot of negatives. So why even bother getting certified? This is a question YOU need to answer. I feel this is a list of valid reasons:
- Obtaining a cert may show you have the personality of someone inquisitive and fascinated with technology. Perhaps you don’t have the experience but you have the “go-getter” attribute to learn anything you don’t already know so you can succeed. Certs can help show that you have a base set of knowledge with gaps being filled in regularly. You should be trying to apply what you learn in test scenarios or in your own home lab. One source of knowledge is not a good idea and it is recommended to broaden your learning with multiple references.
- You may work on certs to fill in gaps of your knowledge, this is personally why I’m becoming certified. I am self-taught, everything I’ve learned is either by on the job learning or after hours learning. Using the certs as a roadmap, I can navigate through features and test myself on my knowledge. Using the results afterward, I can follow up and continue to learn information specifically in areas where I’m lacking. You don’t need certs to accomplish this, it’s just a way to set a baseline.
- Some jobs may require you to obtain a cert after being hired or prior to being hired. Some employers may require the cert in order to receive a pay raise or may base your raise on certs obtained.
- You may want to get a cert to help stand out when applying for jobs. Let’s say there are identical twins, they went to the same school, same job, same employer. They even may have the same name! Except one of those people has a cert, there are no other differences between the two people. They have the same references and accomplishments. I’d pick the person who has the cert because they are the kind of person who did a little bit extra and put forth a little bit more effort than the other person. Obviously, you shouldn’t expect to be picked for a job every time because you have a cert, it just becomes one more thing you can add that sets you apart.
- The last reason I can think of for a reason to certify is to prove and have evidence of competency in that skill set. It doesn’t mean you can solve every problem, it doesn’t mean you are better than the guy you sit next to who isn’t certified. It proves you have a baseline of X knowledge and if your employer asks you about anything in that technology stack, you can say “Columnstore indexes (Or insert any other technology regarding your cert here)? I’ve worked on proof of concepts and testing application through study work. Let’s see what your issue is and make sure this is the best solution for you.”
If you are getting certified, I strongly recommend you make it about the journey and not the end. The end is the finish line, you crossed it, and you get your medal. It’s those hours of sweat and tears that compose the medal. If you achieve that medal through illicit means, it will hold no value to yourself and your employer may realize it holds no value to them either. Companies shouldn’t hire people who go out and get certified, they should hire people because they are the kind of person who goes the extra mile to further themselves and one of those ways happens to be becoming certified. I think there are a lot of other things you can do in your spare time that create value for yourself and your employer, certs do not need to be the only way. (SQL Meetups / SQL Saturdays, taking classes or reading/watching videos and applying that learned knowledge, blogging, helping people online, volunteer work in the community, etc are all great ways to improve yourself too.)
I heard on Radiolab once where a parenting expert was saying that reading a parenting book is not going to make you a good parent. You’re probably going to be a good parent though if you are the kind of person who goes through and reads parenting books. This says you care about the subject, you want to do the best or be the best you can be and you’re going to make that happen. The thing that you achieve in itself isn’t just the point, it’s the fact that you are continuously working until you get the results you strive for that is important. I’d want to hire someone with goals and ambitions, someone who is challenging themselves and taking that initiative. I don’t want to hire someone complacent who shows up for a 9-5 and puts forth the bare minimum.
So let’s get back to the journey. What does that look like for you? Well… what do you want it to look like?
I personally want to be able to say, “Here is exactly how much time and effort I put into achieving this goal”. You can see the books I read, you can see the code I practiced, here are the notes I took, and here are my results showing the outcome of everything. I blog about my test taking experience but more importantly, I blog about how I prepared to take my test. I created thoughtful study guides and used many resources to educate myself; including my own copy of my study sheet which illustrates my journey by day/time spent / resources used.
So is getting certified right for you? Well, you are the only person who can answer that. Maybe you want to do something that shows you are working on yourself, there are many paths to go about it and certifying doesn’t need to be one. It is only one of many tools. And just like SQL, “It depends” and “the right tool for the job” are quotes that matter when thinking about certifying.
I don’t usually comment on blogs but this was a good read. Especially since I’m about to embark on the exact route it appears.
I’m at the starting line aiming for my MCSE in Data management and Analytics. I was searching the web to get a feel of how long it took most people to get their MCSE so I can set some realistic timelines for myself. Three exams in 4-6 months. Is that too steep?
The “paper DBA” comment really got me because I’ve came across certain persons who make heading down the certication path look like a waste of money and unnecessary exam tourture.
I’ve also spoken to those who say,”oh, you’ve been doing this for so long, why don’t you just do the exam, it should be a breeze you have a these years experience”.
It’s really up to the individual to put value to those certifications. For me, it is about the continuous learning journey and the boost of confidence from obtaining that piece of “paper” when I ask for more “paper”$$$$$.
This really depends on your current education level and what is reasonable for you to do. I would estimate I spent about 70 hours of time on the 70-761 and almost 88 hours on the 762. I would guess I’ll be around 88 hours again for the 767 as well, but this time I’m using Toggl to keep track of my study time and method exactly.
Most people I’ve read on seem to be around the 60-80 hour mark when studying and working on these exams. I’ve talked to one person who completed one certificate per month while working to become a DBA. So it is definitely achievable, but it may take some dedication. It would take me about 1.3 hours of studying every day to earn the MCSE in Data Management and Analytics within six months.
You can always pick up the pace or slow down too, I think it’s more of a marathon personally. Be sure not to burn yourself out! See how the first exam goes and let that set the tone for the next few, you can always re-evaluate your study methods and material after the first exam.
Good luck on your exams!
I too am curious about this field. I worked as a lab rat for a couple years and found that I did not enjoy the work. I was looking at MCSE: exams and mySQL job postings when I stumbled upon your blog. I’ve read a few of your posts today and was wondering if you would be willing to make a few recommendations on where to start?
Thank you for your informative blog posts,
– Austin
I think the most important thing you can start doing is attending SQL / Data meetup groups in your area. Networking is going to be crucial to starting in a new field.
The next key piece is going to be your experience. If you don’t have a lot of experience in IT or with SQL but want to go into database, you’re going to need to start somewhere. There may be some analyst jobs that require some SQL that you can move into. I would also look at seeing if your current work has any IT folks you can shadow.
Apart from networking and experience, studying and creating a portfolio will help you get to the interview stage. I think that if you had a few examples of SQL in your portfolio and a cert or two, that would be a good foot in the door for a junior level data job if you are able to find one. Most data jobs are intermediate to senior to start, which is why I recommend gaining experience in any way possible. (Current job is best, working as an analyst elsewhere may help get you there too.)
You can look at my github for ideas on a portfolio. The common ones I list are:
1. The pet database.
2. Change Tracking proof of concept.
3. T-SQL Tuesday Puzzle Challenge. (I had a homework assignment from an interview and it is a showcase piece on my website now.)
4. Any articles that have been re-published or highlighted in the SQL community.
Now for the certifications. I think learning and demonstrating your knowledge is more important here, and networking is THE most important part of the advice I’m giving.
MySQL does have a reputable certification track by Oracle, although less robust than some other certification programs. It’s $245 per exam and they have two listed:
1. Developer
2. Administrator
I don’t have any experience with these exams, but I would assume the developer one would be easier to start with. The passing score required is 61%.
It’s also important to note that SQL Server, Oracle, DB2, Sybase, MySQL, and others are all entirely different database engines. This is important because you are stating that you’re looking for MySQL jobs but wanting to study for a MCSE. These are two different database engines and is like looking for a C# programming job when you are a Python developer. Concepts and theory transfer, but syntax and gotchas between languages differ greatly. So if you do want to study for a MCSE, I would recommend to look for jobs with SQL Server as the primary technology.
You should ideally pick the one you want to work in initially as it will take years to learn one engine well. Once you have learned one and worked in it for 3-5 years, it will be easier to transition or work in others.
I based my choice of SQL Server from the available jobs in this location and what places were looking for. If Oracle or MySQL was more prevalent, I would have started there. Over time though, I have gained experience in many different engines.
Good luck!
Wow, this is a very detailed post! Thank you for being so informative.
Hi, I saw a post of yours on reddit (About MCSA SQL) which linked here and wanted to ask some questions. I am currently in help (hell) desk and desperately wanting out. I got a CCNA RS but it looks like Network Administration is kind of cold (at least in my area, Ontario). I’ve realized I need new skills to get out and was contemplated on further moving up to CCNP but have ultimately decided against it (not unless I get a networking job). I work at an SMB where everyone lives in silos (hard to shadow) and promotions aren’t really a thing.
I’m not sure but I’m hoping learning SQL/Data Analysis can be my way out. Would it be a good idea to start with MCSA: SQL 2016 Database Administration and look for jobs from there? I have almost 4 years of desktop support experience and just want to transit out of that stuff into more challenging and rewarding careers.
Just looking for career advice, any help is appreciated
Thanks.
I would recommend starting with the MTA as it will be better suited for beginners. The MSCA requires two exams, the 70-761 is definitely the easiest of the two but relatively advanced still.
I think there’s good value in networking certs and learning. That’s an area I’ll personally need to revisit for education because it keeps coming up. Throughout my career, system administration, networking, development, and security skills have helped tremendously.
Obviously this is a lot of information. I think it is fine to have breadth here and not depth. Then you increase your specific knowledge in data and databases.
Definitely start with the database fundamentals and work up. You’ll be essentially getting that structured education through the Microsoft certification platform if you achieve the three sql server MSCA certificates.
The major things you should be doing now is finding networking groups and meetups. Usually they discuss jobs and availability. Generally you’ll also learn great information and get some free pizza too.
The last major thing is experience. It may be worth stepping into a more advanced role not in database and segway into it. Like networking or systems administration. My process was jack of all trades, to systems administration, to pseudo dba, to real dba. Getting into data isn’t the easiest but it’s very doable and rewarding. Constantly be learning. Other traits that can help : volunteerism, happy, friendly, honest, and communicative. These will help more than you’d think.
At almost four years, you are probably more than ready to move onto your next company. I’d be constantly applying and interviewing for roles that advance your career. As long as it’s forward, it’s hard to go wrong. You know your life best though, so keep that in mind and do what’s best for you. It’s easier to take risks when you are younger and it gets more difficult to make jumps the more your life has dependencies. Good luck! Let me know if I didn’t answer your questions well enough or if you have additional ones. I’ll be able to answer more once I’ve returned from Jamaica.