196: I wish I knew this before I learned SQL

Here are the seven things I wish I knew before learning SQL number one. SQL is incredibly easy and insanely complex at the same time. And let me explain. SQL is like an iceberg. In fact, there is a famous sequel meme with an iceberg with a different layers of SQL that you could possibly learn in your data career. And honestly, the first half, the first little bit of the iceberg is really easy to learn. The commands that you need to learn as a data analyst are really not that hard to learn. They're easy to get a hold of eventually, and there's really only 17 of them that you need to know. We'll talk about those here in a second. But the crazy thing is it's also insanely complex. There's like a bajillion different commands you could know in sequel, and there's so many different levels and layers to it. There's a bunch of stuff that I don't even know. So for example, if we look at this iceberg meme right here, like you'll see that the easy things are at the top. The order buy and the group buy, and the limit and the null and joins and stuff like that. And then it gets more and more complex as you go down. Like for instance, even in the third layer, lateral joins, I've never even used lateral joins. Cursors never used those as well. Triggers I have used a little bit, but my point here is it goes so far down where it's like in this second to last layer down here, like with the narwhal, I don't even know any of that at all. So my point here is you can make it like me, senior data analyst, who's worked in the field for 10 years, who teaches people data analytics. And you could not even scratch a service of sql. And that's perfectly okay because I know the first two to three decently, well, the first two at least, and it solves like I would say, 90% of data analysts problems. And we'll actually talk about that here in a second. What is a SQL problem or a data problem that someone, a data analyst actually solves with sql? Because not all of SQL commands are made for data analysts. So in my opinion, if you're just getting started, you can get by with like 17 SQL commands and they are the following ready. Number one, select number two from number three. Where? Number four. Group by number five. Order by number six. Like number seven, count. Number eight, max in min, uh, number nine, average number 10, some number 11, case when number 12, join number 13 distinct. Number 14, having number 15 with number 16 partition by, and number seven, uh, 17 concat. Now there's some other ones you possibly could use as well, like Union is another one that probably is used pretty often. Um, maybe you could ar argue like some sort of rank would be useful, um, or some sort of like day function or something like that. But my point here is there's really not that much to get started with. Like if you can get those 17 things down, you can land a day job a hundred percent. And I honestly think you can learn those 17 things in like three weeks if I'm being honest. And that's how fast I teach them. Inside of my bootcamp. You know, I run data Alex Accelerator, it's a bootcamp. We teach SQL and we do it in two weeks. The sequel portion, and I think that's good enough to land your first data job. If I'm being honest. Now, that's about 30 hours of work probably, but I literally think if you spend 30 hours on this, you can learn it pretty easily. By the way, if you found this list helpful, I send out a weekly newsletter with tips just like this, and you can join 30,000 other aspiring data analysts to get these weekly tips in your email@datacareerjumpstart.com slash newsletter, or there is a link in the show notes down below. But sign up because I send awesome stuff like this every single week. That actually brings me to my second point, which is that you don't have to have all your SQL syntax memorized. It's basically impossible. Like I showed you, there are so many different commands that you could be learning so many different commands that you could be using, and you might be using Excel, you might be using Tableau, you might be using Power bi, might using Python, all on top of SQL as well. And those have different syntaxes and so it's really hard to remember all the different syntaxes, so you don't have to have it memorized. It's not a problem if you forget. I forget all the freaking time it happens. N nearly like. Every day, to be honest, probably more than I should tell you guys on YouTube, but I'm forgetful. I've never been a good memorizer. And the cool thing is you don't have, you definitely don't have to have it memorized for the job, right? When you're at the job, there's not like someone over your shoulder like making sure you know how to do this. Now, you should obviously know the basics. That's, that's a given, like select from group by those where those types of things. You should definitely know the backbone of sequel, probably by, by heart or by hand. Um, but like the more complex stuff, the more syntax stuff, you definitely don't have to know. Um, where this might not be true is in an interview, in an interview for some reason in the data world, we just love to, Hey, do you have this memorized? No, you suck. You're never gonna get hired. You reject you. Like that's just how it is. I don't know why it is. I hate interviews like that, but there are some sequel interviews that do kind of treat you that way. I think it's basically like if you don't know that you don't know enough to do the job, but I don't agree with that interview process, but that's just how it is. So just telling you that to be prepared, uh, especially in today with like a lot of these editors that will actually like, kind of fill in the syntax for you or suggest syntax for you. With chat, GBT, with Claude, with Google, like you really can figure out what you need to do or, or how to do what you wanna do in a moment's notice. And so memorization, the need for it is just going down. I don't think you need to be memorizing something and you shouldn't feel bad if you don't have things memorized. Number three, there's actually a ton of beginner sequel commands that you may learn in an online tutorial that are absolutely useless and you should really never use them. Or rather you won't use them in your career. And the reason is. Is data analysts. We do a lot with databases, right? But really, most of the time, I'd say 90% of the time, we don't actually create, alter or delete databases. We aren't really managing databases. We're querying databases, which, querying is a funny word. It basically means you're asking questions to the data. That's your job as data analysts is to query the data in the database. And so really data engineers, data architects. Uh, maybe an analytics engineer. Their job is to more create the database structure and everything like that. Your job as data analyst is just to answer business questions with the data that they provide you. And so there's certain things and certain tutorials that will tell you that you need to know some commands, like insert or delete or update grant or provoke, and you don't need to know those. You don't need to know those at all. That's like more data engineering and they often call those DCL and DML, which stands for data control language and data manipulation language. And basically, in my opinion, you don't need those at all within sql. If you're gonna be a data analyst, at least not at the beginning. Like don't waste your time. And I'm telling you, if you go to, if you like Google SQL tutorial, one of the first things they're gonna teach you is like, okay, this is how you create a a table. This is how you delete a table. This is how you update a row. Do insert into to populate your database. And those are good things to know. I'm not saying like that's a bad thing to know. I'm just saying if you're in a crunch for time, which we all are today, and if you're a career pivot. You don't have unlimited time, so you have to figure out what to spend your time on, and I'm telling you, I wish I wouldn't have spent time on this. The fourth thing I wish I knew when I was starting SQL is that you actually don't even really have to know SQL. Now. SQL is really in demand, like it is the most in demand data tool out there across all the different data disciplines. That being said is like everything that you can do in sql, you can kind of get away with. In some other data software. So for example, a group I in SQL is really just a pivot table in Excel and you can do the exact same manipulation. Inside of Pandas as well with a group by function there. You can join Excel tables. You can join Google Sheets, Tableau and Power BI both have a bunch of no code data manipulation tools built into their softwares so that you can actually do like a bunch of data manipulation that you could do in SQL inside of their softwares without having to write SQL code. I really think you should learn sql. I think it's worth your time. But that being said, just know that you can do everything that you can do in SQL in a different software. So if you're an Excel master, you can probably figure out how to do whatever you need to do to the data that you would do in SQL inside of Excel. You don't have to learn every single data tool, and if you try, you're gonna be like a hundred years old before you actually ever feel ready to apply to any job. My point here is just don't feel that bad if you don't know sql, but you should probably learn it anyways. Tip number five is that you need to have an IDE and an IDE stands for Integrated Development Environment. And what does that stand for? Well, when I was first like breaking into data, I knew software, I knew Excel, for example. Uh, and when you download Excel, you hit download Excel, and then you can, you know, click on Excel and it opens up Excel and then you can analyze data inside of Excel. Well, SQL is a little bit more complicated than that. First off, there's not just like one software that's called SQL and you hit download on sql. There's a bunch of different flavors and different like sub languages of sql. Um, the more popular ones are MySQL, SQL Lights, Microsoft SQL Server. Um, Snowflake's becoming more popular. Uh, but my point in telling you this, if you were to download, for instance, MySQL, you wouldn't be able to just like double click it and it would open up and you can analyze data in sql. You need what's called an IDE or often SQL's called a workbench. And basically this is like a secondary or like a companion software that comes with the actual download of SQL that lets you use it in a non terminal, non-car coder way. So just know when you're going to download sql. You probably need to download some sort of an IDE or some sort of a workbench for you to be able to use it, and that's a little bit confusing and a little bit difficult to set up. This is one of the reasons why when I teach SQL inside of the data analytics accelerator, we actually do the first week without downloading an IDE or even downloading anything. We actually just use a SQL version inside of the cloud. That allows you to just get the hang of SQL, of the actual language before you have to deal with like the annoying logistics of downloading and installing. 'cause that's a pain in the butt always. I've done it like literally a hundred times and I hate downloading SQL every single time I do. It's a pain in the butt. Just trust me. It's not fun. But hey, if I went back and I could tell myself one thing, I'd be, Hey, you need an id. If you're just gonna try to do it without an id, it's not gonna work. That brings me to my sixth tip, and that is that you need to use the limit function in sql. If you run a SQL query, SQL will give you back all the matching rows that match your query. And a lot of times if you're using a big database, that could be, you know, it could be five rows, but it could also be 50 rows. It could be 500 rows. It could be 5,000 rows. It could be 500,000 rows. It could be 5 million rows. If you're trying to return 5 million rows, it's gonna take a long time to return that, uh, especially if you're maybe not the best at optimizing queries and stuff like that. So my advice to you is to make sure you're using the limit at the end, and that will actually, like if you do limit to 10, that will only give you the first 10 out of the 5 million, so that way you can test your queries first. You know, on a smaller result base, so it's fast. And then once you're sure that the queries kind of work in the way that you want, you can take that limit from, you know, 10 to 100 to 1000. And then you can make sure that everything's still working the way that you want, but you don't have to wait very long. The seventh thing I wish I knew is that getting good at SQL doesn't equate to actually getting hired because a lot of you guys probably watching this right now are applying data jobs. And you're getting rejected. You're getting rejected. You're not even getting like an interview, right? And you're like, oh man, I just gotta get better at sequel. It's like, why, why do you think that you, you're probably already proficient enough at Seql. Or if you're not, like I said, you can get there in like a month. So if you're gonna go like, you know, hit leak code really hard or just like practice seql problems, that's not gonna equate to landing a job. It's just not, because right now you're not getting rejected because you're not gonna a sequel getting rejected for some other reason probably that your resume and your LinkedIn aren't good. Um, and so really when it comes down to it, SQL is just like. Maybe one 15th of landing your first data job. In my opinion, it's just one third, it's just a skill, right? So I have this method, it's called the SPN Method Skills Portfolio Network. You need all three to land a data job. Most people are just focused on the S part, the skill part, and SQL is just one part of the S part. So it's like one 15th of the whole equation. And if you're just focusing on sql, you're missing out on so much more, like your portfolio, your projects, you're networking, your cold messaging, your resume, your LinkedIn. And so it's important to get good at sequel. Yes, I'll give you that. But it's also important not just to get stuck in the grind of doing these sequel problems over and over and over again, thinking that's somehow gonna magically get you a job. Because it's honestly not. And if you do wanna know what's gonna get you a job, it's actually following the full SPN method. So that's of interest to you. If you've never heard of the SPN method before, I will have a link down below to learn about the s PN method. And I also have a link to my bootcamp, which literally will teach you to become a data analyst from wherever you're at, to landing your first data job, following the SPN method, step by step, step-by-step with instructors, with peers, and a lot of fun. So hope to see you guys there.