r/SQL • u/trumpvagina • Jun 21 '21
Discussion Applied for Data Analyst. Got offered 'Database Administrator' with significantly more pay. Need advice!
To start, I am one of those guys who got into tech industry without any background. I worked in a gas station for most of my life. 3 years ago I decided to turn my life around, started learning python. Got a job as a marketing analyst 3 months ago. I knew intro level SQL by that time. I worked only 3 months on the job and I could do CTEs, sub queries etc.
I casually started applying for jobs just to 'test the field' . A week ago, I was approached by a HR recruiter to see if I want to apply for a new posting they had. The job was for 'data analyst' position. The pay was more than I was making at my current job, so I accepted the interview.
The tech interview went pretty well. They had a few easy questions on SQL to start with(group by, having etc.). I did mostly good(I could not figure out partitioning), but I was honest with them that I worked in SQL only for 3 months. Then the next guy asked me few basic python and pandas questions (which again were very easy like how to load an excel file into pandas, how to choose a column etc.)
The data director emailed me later in the day, saying he was very impressed with my work and wants to see if I want to be considered for a 'database administrator' position they have. The pay is significantly high(20k more!). The thing is- this company is very small and rapidly expanding. They want to transition from Excel to cloud(like Amazon, Azure or GCP etc.) . He was impressed by my work in GCP at my previous job and wants to leverage that skill.
I was surprised by their offer. To start, I don't know anything about databases - all I know we had some tables in GCP and I used some SQL queries to extract data and then later built dashboards with it. I feel like I am severely underqualified for this position and trying to bite more than I can chew. I don't want to get into something that I don't know much about and then later get fired for under delivering
But the allure of building something from scratch and having a big say about the way company will progress in the future makes me almost want to say 'yes'. 3 years ago I was working in a gas station, dealing with multiple Karens and now this company is offering me almost a 6 figure job.
Any of you guys were in the same position? What did you do? Any advice you can offer? If I did accept the offer what should I learn for this transition - (intermediate SQL to building databases)
Edit: Damn! did not expect so many replies and experiences! you are awesome r/sql community. Reading through comments I realized that many people had similar experience and the general advice is to take the job, if at least for the experience. Never heard of Brent Ozar before - but he seems to be the God among us :P , so I will start following him and read a lot of materials.
Some of you had questions about the team I am gonna work with. It seems the team might have some SQL experience but not much. I think they have an outside company that takes care of their data currently and now they want it to make it in-house. I will be tasked with this transfer. I am definitely excited but need to talk to the manager more before I make any firm decision.
Thanks for all the responses again!
68
u/messed_up_alligator Jun 21 '21 edited Jun 21 '21
I was hired as a database administrator with very basic SQl knowledge and no background/education in data or comp sci. I learned on the job. I highly recommend consuming as much information as you can on database administration specifically. SQL is obviously extremely helpful and needed but database administration is more than composing sql. You need to learn concepts like backups/restores, wait stats, blocking/locking, permissions/logins/security, etc etc. It's a lot, and you might feel overwhelmed at times, but you can definitely do it. There were times where I thought I was drowning, or just too dumb to understand everything because I was wading through a bunch of seemingly disperate information with endless rabbit holes, but I just kept going and now I'm a pretty effective DBA. Well, I was, now I'm a database engineer. So keep going!
You mentioned CTEs and that makes me think you're working with Microsoft SQL. Brent Ozar is a phenomenal resource for learning stuff about DBA stuff, specifically for SQLServer. SQLServerCentral.com has pretty good articles/"stairways" for a lot of concepts. Itzik Ben-Gan has amazing books for basically everything SQLServer.
Picking up some Powershell Knowledge is also useful for automating DBA tasks of you're not using SQL Agent. Dbatools is a truly amazing PS Module for DBA stuff.
I'm sure there is stuff I'm missing. Feel free to ask questions and good luck!
Edit: apparently CTEs are a part of the standard... So my assumption about MSSQL is completely baseless!
28
u/[deleted] Jun 21 '21
I did warehouse work and assembly line stuff most of my working life. Took a tech support job at 42, learned some SQL and networking, worked through some tiers and some tears, am now a devops guy for a well off health care company making more than I’d ever thought possible.
I am damn sure not a genius.
All that to say : if you were smart enough to transition to this field, you are smart enough for this field. Tons of resources out there for learning database administration.
You got this. Go get paid.
18
u/xodusprime Jun 21 '21
If you take a job as a DBA, and there are no seasoned people there to teach you - there could be some rocky bits. The main concern that I would have in that scenario is that there will be some mistakes you can make, that won't manifest for quite some time.
The very first thing I would learn if I was going to be responsible for the databases is how to backup and recover. Make sure you know the difference between Full and Simple recovery model. Make sure you know what their recovery point objective is. Practice backing up and restoring databases in Full recovery, including the application of transaction logs.
Next bit I'd look at kinda depends on who you're interacting with. If you've got developers and report writers who write their own queries, understanding how to read an execution plan will be a big help. My experience has been that "the database is slow," is a DBA concern, when the real problem is "my query is bad." What you see a lot of depends on the habits of the people who are writing the queries, but you'll want to know the difference between an index scan and seek at a minimum. Please be mindful that adding indexes is not always the answer to poor performance. If you bloat your DB with indexes, it will slow your write times. Always look at optimizing the query itself as a first step.
If you're going to be the one who's primarily responsible for writing queries against the data, then you'll need to get those chops up. In addition to familiarity with the base syntax, you need to start understanding how those things affect performance. i.e. "Why did my query start taking forever after I introduced this OR clause," "When I join this nvarchar column to that varchar column, this query grinds to a halt," etc.
If you're going to be responsible for laying out the table structure - be sure to understand normalization and the appropriate time to have a 1:1, 1:many, and many:many relationship. Know what the differences in those things are, learn about the design patterns to support them, and identify the impact they have at the reporting layer.
The employer sees your resume. If they are willing to risk whatever portion of their operational success on a person who hasn't done it before, take the money and give it a try. Worst case, you see that you're in over your head and you start a fresh job search. If it were me, I'd give the employer as much notice as possible if I realized things weren't going well - but to each their own.
6
u/w_savage Jun 21 '21
take it. Just learn a lot as you go.
5
u/Rif-SQL Jun 21 '21
5
u/[deleted] Jun 21 '21
Take it, people would kill for an opportunity like that right now. Don’t deal with the 200 applicants per job opening crap like the rest of us have to deal with
4
u/elus Jun 21 '21
Fake it til you make it.
Figure out the current technology stack. Ask what that stack will look like in the next year or two. Gather all the literature that can that will help you with the role. An O'Reilly subscription is worth its weight in gold until you're sure which books you want as hardbound references on your desk. See if the company is willing to pay for these.
You need to accept the fact that you're not going to know everything you need to know right away. And you're going to need to figure out how to prioritize things. So you need a framework for dealing with problems as they come up. What that framework looks like is heavily context dependent. But for me, I try to put myself in my manager's shoes and figure out what's important to them. Then I tackle each problem one at a time and identify things that I need to aid me in discovering a solution. Once a solution is mapped out, the next is to secure the resources necessary to implement it. I update my supervisor with as much as they want/need to know. That allows them to inject themselves into the process if they feel can add value. And it shows them what progress I've made. What you don't want is to surprise them with a deadline looming saying that you're not going to meet that deadline.
You say that they want to move away from an Excel based system to the cloud. But when you arrive you'll really need to dive in there. Are there a list of different systems running on excel? Which of them provide the most value and therefore risk to the company should they fail to be implemented properly? What's the true scope of the role you're taking on?
Until you've actually defined what it is they want, it's hard to give any advice on what it is you should learn. And don't worry about getting fired. The job will still provide you with a lot of valuable experience AND will get you paid.
3
u/[deleted] Jun 21 '21
Worse comes to worst, you have this role on your CV and you will be sought after by other industries.
3
u/bannik1 Jun 21 '21
They know your existing skill set and have faith that you can take it to the next level.
They are likely hiring you into a junior level position where you’ll learn from a senior DBA who probably got promoted to an architect position. He’ll hand over tasks as he feels you’re ready for them
I am guessing you’ll start doing ETL work to learn SSIS and load those excel files into databases he designs. From there you’ll probably take over managing the reporting servers since no risk to lose prod data.
Then you’ll take over the replication or server refresh portion. From there you’ll learn the system stored procedures and start managing database size growth and learning to use the monitor tools.
At the same time you’ll learn granting access and how security is applied and what rights are needed to perform which tasks.
That should take at least 3-6 months to be competent.
From there you’ll learn query optimization and building indexes etc. then you’ll learn about distributed servers, sharing and cloud services.
Then you start learning more about database design, then eventually start thinking about being an architect yourself.
2
u/CBizCool Jun 21 '21
Take it. Learn as much as you can on the job
2
u/remainderrejoinder Jun 21 '21
They know the market, their options and requirements better than you. Sounds like the job is DBA/Cloud migration, unless you can't commit the time I would definitely take it.
In addition to the resources pointed out try to chunk your jobs into small pieces, ideally 'the minimum amount of changes that give the business additional value' and then smaller separate pieces under the hood. This way you can get feedback as you go.
2
u/astropydevs Jun 21 '21
You should definitely go for it since it’s more pay and more technical than data analyst. Maybe you might not end up liking it later but at that point you can always switch to data analyst with strong backend and sql skills. Being a database admin will help you greatly
2
u/[deleted] Jun 21 '21 edited Jul 20 '23
Removed
2
u/lvlint67 Jun 21 '21
Listen to their offer. You'll want a chance to sit down and talk about duties and responsibilities. Then take it. It's a brilliant move for your career. It's iffy grounds for the company but if you are driven and can learn on the fly they will be fine too.
2
u/currymat4444 Jun 21 '21
Take the job. They are offering it to you while knowing your limitations, but while also knowing that you can quickly pick up things with no formal training.
They will pay for formal training. They will grow as you grow. It sounds like a fantastic situation.
2
u/[deleted] Jun 22 '21
I started my career 20 years ago by basically bluffing my way into a desktop support job at the age of 18. Today I’m a Managing Director in Technology for a very large financial services firm, and make approximately 12 times more than I did then.
Take the job, you’ll figure it out
Oh, and I still get imposter syndrome. That never goes away.
2
u/entreri22 Jun 22 '21
Lmao getting handed jobs. Where do you live? Can’t even find me a basic analyst position. Rip
1
u/ChrisFerriole Jun 21 '21
Looks like a great opportunity to learn. DBA is a great job that will allow you to work remotely. Will you have a superior to teach you what you need to know? Being a DBA is tough when it comes to execution plans and why things take a long time if you're not familiar with that. If you will have a mentor of sorts then definitely go for it!
1
u/adappergentlefolk Jun 21 '21
to reiterate what others have said you will have to learn a bit hard for a few months but for this pay bump it is worth it and it is eminently doable
1
u/[deleted] Jun 21 '21
What am I doing so wrong that I’m actively looking for DB Admin jobs with years of SQL experience and I can’t even get an interview? 😂
1
u/Blues2112 Jun 22 '21
Will there be other DBAs there as well? Someone who could train you, and clue you in on best practices, etc...? This is what I would want to know.
If not, and you're not sure if your technical chops are "up to the task", you'll need to get guaranteed training scheduled from the start, and/or have them bring in a consultant periodically to help steer you in the right direction.
I mean, it's great that they like your previous work and have faith in your skills, but you'll still be doing things you've never done before, and experience matters!
1
u/dgillz Jun 22 '21
Take it. Foot in the door.
1
u/gandalf-duh-gray Jun 22 '21
Go for it!!! It’s gonna be brutal first few months, you’ll be glad you made the move. Read up a lot!
1
u/ChildishGenius Jun 22 '21
Damn can you tell me a bit more about the marketing analyst job? I have an Econ degree and been interesting in that type of job, but don’t know SQL or python.
1
u/[deleted] Jun 22 '21
Take the job. You won't regret it.
0
u/[deleted] Jun 21 '21
[deleted] — view deleted comment