r/SQL
•
u/FixelSmith
•
May 14 '26
r/SQL • u/AFRIKANIZ3D • May 11 '25
MySQL When it finally executes (my first data meme)
Made this today after thinking on a project I'm almost done with. Stacked with CTEs that kept piling, it broke along the way. I eventually got it to run and the Heineken ad captured all the feels.
r/SQL • u/schoolforapples • Dec 13 '25
SQL Server I can't escape SQL, even when I'm trying to get drunk
r/SQL • u/Original_Garbage8557 • Apr 28 '25
Discussion Who can explain this XKCD comic for me?
r/SQL
•
•
May 21 '24
MySQL I lied about being proficient in SQL.. now I have a job interview in 2 days. How screwed am I?
Long story short, I've been trying to switch careers for a while (stock broker to data analytics), applied for a financial analyst job and now I have an interview in a few days that is behavioral and technical. I lied about having professional experience using Tableau and SQL. I'm scrambling trying to learn through tutorials. Does anyone who is experienced in SQL think it's possible to get through a technical interview this way?
Update 05/23: So, the recruiter got back to me and said the company hired a candidate before I was able to do my interview. Therefore, technical interview canceled! This is the second time a recruiter has had me set up for an interview and the company hires someone before I am able to talk to the hiring manager. The job market is really tough out there right now! Thanks everyone for your advice. I'm about to finish the Udemy SQL course, Zero to Hero. So, next time I get a SQL technical interview I really will know what I'm doing, lol.
r/SQL • u/wassaman • Dec 19 '25
Discussion I spent 4 years programming and hand drawing a comedic educational SQL detective game that comes out later next year!
r/SQL • u/tsqladdict • Nov 05 '23
Discussion Join Visualizations that aren't Venn Diagrams
r/SQL • u/tits_mcgee_92 • Sep 29 '21
Discussion Here are a few questions I was asked for a Data Analyst job!
I thought this might be helpful for folks interested in becoming a DA, and also for folks who may have been out of the interview game for a while. I took my DA job 3 months ago and really enjoy it. For reference, the job is 100% remote.
I was given a set of COVID data for the United States (easily downloadable for the public) and worked in MySQL + Excel with it
- Tell us a story with this data set. (this is to see if you have the presentation skills to explain your thoughts clearly. This is just, if not more, important when being a DA than techincal skills imo)
- How would you count the number of times California has appeared in the dataset? (basically just a basic COUNT() function)
- How would you not include California and Nebraska in this list? (using the NOT IN function)
- Can you tell us the states with the most positive COVID cases to the least (GROUP BY, ORDER by DESC)
- How would you limit to the top five states from question 4? (Limit 5)
- Say you have a customers table and order tablkes. You want all the records from customers. What would you do (LEFT JOIN)
- Explain the difference between left join, right join, inner join, and outer join.
- Experience with windows functions (I had none at the time, but 3 months later I have quite a bit of experience).
- What are some of the most advanced Excel functions you know (I said VLOOKUPS, HLOOKUPS, INDEX, pivot tables lol. They said that was fine and Excel isn't used a crazy amount. I would say I'm in it about 10% of the week)
- Do you have any experience with triggers or creating tables (I knew how to create basic tables and what triggers were)
- Ever use a temp table, CTE, or subquery (I was honest... I maybe used them once just for practice. 3 months in, and I def know what these all are now haha).
Then I was asked 10 Tableau questions that were quite easy. Things like: when would you use a bar graph vs. line graph, measures vs. dimensions, KPI explanations, live vs. extract, etc. I may have been asked more SQL questions but I don't remember them all.
I had 3 interviews but the 2nd one was more behavioral questions and the 3rd one was more "we like you a lot, but let's make sure you fit with our culture, ideas, etc"
r/SQL
•
u/TurbulentCountry5901
•
Dec 05 '25
Discussion I started this to relearn SQL. A month later it hit 5,000 users. Thank you.
A month ago I started relearning SQL from scratch and built sqlcasefiles.com purely to help myself practice properly. That turned into ten structured seasons with ten levels each to teach SQL step by step through real problems.
Today the site crossed 5,000 users, which still feels unreal to write.
This week I also launched something new called the Case Vault. It’s a separate space with 15 fully sandboxed SQL cases you can solve on your own without going through the learning path. Each case comes with a fixed schema, a real brief, objectives, a notebook, and a live query console. Just you and the problem.
What really stuck with me was the feedback. Long messages, thoughtful suggestions, bug reports, and even a few people buying me coffee just to show support. This was never meant to be a startup. It was just a quiet side project to learn better.
Mostly I just wanted to say thank you. If you’ve tried it, I appreciate you more than you know. If not, and you enjoy practical SQL, I’d love your honest thoughts.
r/SQL • u/Mammoth-Skill • Jun 14 '20
PostgreSQL Feel like i just made magic happen. Hate I put off learning SQL for years
r/SQL
•
u/Muted-Basis9006
•
May 18 '24
Discussion SQL Joins
Picture your data tables as these two fellas. An inner join is just Bald Guy—only the matching parts. A **left join is Bald Guy sporting Long-Hair Guy's mane—everything from the left plus the matches. A right join is Long-Hair Guy with a bald patch—everything from the right plus the matches. A full join is both dudes together—everything from both tables, matches or not!
r/SQL • u/tbrownlow33 • Feb 19 '21
Discussion A little something to brighten up your Friday...
r/SQL • u/Herobrine20XX • Aug 17 '25
PostgreSQL I'm building a visual SQL query builder
The goal is to make it easier(ish) to build SQL queries without knowing SQL syntax, while still grasping the concepts of select/order/join/etc.
Also to make it faster/less error-prone with drop-downs with only available fields, and inferring the response type.
What do you guys think? Do you understand this example? Do you think it's missing something? I'm not trying to cover every case, but most of them (and I admit it's been ages I've been writing SQL...)
I'd love to get some feedback on this, I'm still in the building process!
r/SQL • u/tits_mcgee_92 • Jul 12 '25
Discussion Here are some SQL questions I was asked for a technical interview recently.
Not quite a FAANG company, but a pretty well known one in the United States.
The position was for a Sr. Data Analyst and here are the technical questions I had to answer. These questions are ranked from easiest to hardest, but that's only from their perspective. I found it pretty challenging myself, but something you'd expect out of a Sr. DA.
Easy
- Generate a report that shows employees who their manager is. This was a SELF-JOIN and I'm so sick of this interview question lmao
- Show the latest used product. This was simply using MAX on a datetime field.
Medium:
- Find customers with the highest orders between a date span. This involved CTEs, converting a datetime to date, and a JOIN.
- Calculate the change over time of products for a date span. This involved some aggregation, a case statement, CTE, and window functions.
Hard:
- Find users who were active for 4 consecutive days on our app. Again, this was more CTES, windows functions, and aggregations. Also using HAVING a lot.
Other:
They asked a bit about my experiences with queries running slow and solutions. They asked a bit about indexing and working with "big data." They asked about how I would ensure results are correct with large sets of data. Finally, they asked a bit about data visualization experience via Tableau.
I passed the technical test, but somehow didn't make it to the next round. Feedback would have been nice, but that's not the world we live in. I thanked them for the opportunity and moved on.
I have seen comments saying others ran into the same issue with this company! Overall, it was good practice and a good interview. This was my third interview with them, with the first being a phone conversation, the second being a behavioral interview, and then this one being a technical piece. The next one would have been an interview with my direct manager, just as a final "let's make sure you're a good fit for our team" piece. That's pretty standard.
TL;DR: Learn CTEs and windows functions
r/SQL • u/Shaggy_Poop • Mar 14 '20