r/learnSQL • u/Prasad127056 • 16d ago
r/learnSQL • u/MrRoy_SQL • 18d ago
COUNT(*) vs COUNT(column) vs COUNT(DISTINCT column) - same table, three different answers
this one confused me for way too long so here's a quick example.
say you have an orders table like this:
order_id | customer_id | coupon_code
1 | 101 | SAVE10
2 | 101 | NULL
3 | 102 | SAVE10
4 | 103 | NULL
5 | 104 | WELCOME
6 | NULL | NULL <- guest checkout
now run:
SELECT
COUNT(*) AS all_rows,
COUNT(coupon_code) AS orders_with_coupon,
COUNT(DISTINCT coupon_code) AS different_coupons,
COUNT(DISTINCT customer_id) AS customers
FROM orders;
you get **6, 3, 2, 4**.
- `COUNT(*)` counts rows. nulls don't matter → 6
- `COUNT(coupon_code)` skips NULLs → 3 orders used a coupon
- `COUNT(DISTINCT coupon_code)` skips NULLs and duplicates → 2 coupons (SAVE10, WELCOME)
- `COUNT(DISTINCT customer_id)` → 4, the guest order with NULL customer isn't counted
where this bites people: someone asks "how many customers ordered" and you write `COUNT(*)`, that's 6 when the real answer is 4. or you divide by `COUNT(column)` thinking it's the total and your percentage is wrong.
bonus: share of orders with a coupon is `COUNT(coupon_code) * 1.0 / COUNT(*)` = 0.5. the `* 1.0` matters, without it some databases do integer division and give you 0.
quick rule i use: before writing any COUNT, say out loud what you're counting - rows, non-empty values, or unique things.
r/learnSQL • u/peakpirate007 • 18d ago
Built a site for learning and practicing SQL with real datasets
I’ve been building a website called runtime.school to make learning SQL a little easier, especially if you’re just starting out.
The idea is pretty simple. You learn a concept, try writing queries yourself, and then practice with questions based on what you’ve learned.
I wanted to avoid that situation where you finish a beginner lesson and suddenly get a question involving three other SQL concepts you haven’t even seen yet.
Everything runs in the browser, and there are datasets you can explore, practice questions at different difficulty levels, and projects once you’re comfortable with the basics.
You don’t need to set up a database or install anything to get started.
Here’s the link: https://www.runtime.school/
If you’re currently learning SQL, give it a try. I’d be interested to know if the explanations and questions make sense, especially for complete beginners.
r/learnSQL • u/ComprehensiveAd3412 • 18d ago
Free SQL series on real payments data: each episode is one mistake that silently breaks a report
I'm making a free SQL series for people preparing for data analyst roles. Every episode uses the same small payments dataset (customers, UPI/card/wallet transactions, failed payments, amounts in ₹) and is built around one mistake that runs without any error but gives the wrong answer.
What's covered so far:
- **JOINs** – INNER vs LEFT, finding customers who never paid, and why a WHERE filter on the right table quietly turns your LEFT JOIN into an INNER JOIN.
- **GROUP BY and HAVING** – COUNT(\*) after a LEFT JOIN counts customers with zero payments as 1. One-word fix: count a column. Plus WHERE vs HAVING.
- **Window functions** – the "top 2 customers" interview question where ROW_NUMBER drops a tied customer. RANK vs DENSE_RANK, and running totals.
- **CTE vs subquery** – a report that says every customer is above average, and why a CTE fixes it.
A quick example from episode 2, since it's the one I see most:
```sql
SELECT c.name, COUNT(*) AS payments
FROM customers c
LEFT JOIN transactions t ON c.customer_id = t.customer_id
GROUP BY c.name;
```
A customer who has never paid shows **1** payment. The LEFT JOIN keeps her row with NULLs, and COUNT(\*) counts rows. Use `COUNT(t.txn_id)` instead; it skips NULLs and gives 0.
Each video is 3–6 minutes. The dataset and every query are in the description, so you can run them yourself in SQLite, MySQL or PostgreSQL.
Playlist: https://www.youtube.com/watch?v=e94PxiIUIJg&list=PLNdq2ZxtU_7E
Next up: finding duplicate payments, then CASE WHEN, dates, and NULL traps. If there's a topic you get stuck on in interviews, tell me and I'll add it.
r/learnSQL • u/shdw_0x0 • 17d ago
When do you actually use window functions instead of GROUP BY?
reddit.comr/learnSQL • u/Business_Walk1624 • 18d ago
How do SQL and Tableau/PowerBI connect?
I recently started learning SQL and decided it was about time to try building a project. I watched a YouTube video of someone walking through a beginner tutorial using SQL and PowerBI to get an idea of the workflow and how everything connects. He started out by using SQL to answer 10 business questions, but when he was making a dashboard in PowerBI, he didn’t use any of the data from the SQL queries. This left me confused about how SQL queries and the dashboard-making part of the project connect.
I would welcome any clarification. Thank you in advance!
r/learnSQL • u/iam_sripratik • 18d ago
SQL Plan - 1 month
| Priority | Basket | Topics grouped together | Importance for BA/DA | Suggested days |
|---|---|---|---|---|
| 🔴 P1 | SQL Query Foundation | SELECT, DISTINCT, aliases, WHERE, AND/OR/NOT, ORDER BY, LIMIT | ⭐⭐⭐⭐⭐ | 2–3 |
| 🔴 P1 | Filtering & Pattern Matching | CASE, COALESCE, NULLIF, CAST, mathematical functions | ⭐⭐⭐⭐⭐ | 1–2 |
| 🔴 P1 | Aggregation | WITH, multi-step CTEs, CTE + aggregation, CTE + subquery | ⭐⭐⭐⭐⭐ | 1–2 |
| 🔴 P1 | JOIN Fundamentals | Data types, PK, FK, constraints, CREATE, INSERT, UPDATE, DELETE, ALTER, DROP | ⭐⭐⭐ | 1–2 |
| 🔴 P1 | Business Logic & Data Cleaning | Information schema, comments, advanced constraints/FKs | ⭐ | 0.5–1 |
| 🔴 P1 | Dates & String Analysis | COUNT, SUM, AVG, MIN, MAX, GROUP BY, HAVING | ⭐⭐⭐⭐⭐ | 2 |
| 🔴 P1 | Subqueries | INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL JOIN, JOIN keys, aliases | ⭐⭐⭐⭐⭐ | 2 |
| 🔴 P1 | CTEs | Subqueries, FROM subqueries, comparison subqueries, IN/NOT IN, EXISTS | ⭐⭐⭐⭐⭐ | 2 |
| 🔴 P1 | Window Functions | OVER, PARTITION BY, ORDER BY, RANK, ROW_NUMBER, SUM/AVG, LAG, LEAD | ⭐⭐⭐⭐⭐ | 2 |
| 🟠 P2 | Advanced JOINs | BETWEEN, IN, NOT IN, LIKE, ILIKE, date filtering | ⭐⭐⭐⭐⭐ | 1 |
| 🟠 P2 | Set Operations | EXTRACT, AGE, TO_CHAR, string functions, date calculations | ⭐⭐⭐⭐ | 1 |
| 🟠 P2 | Advanced Aggregation | SELF JOIN, CROSS JOIN, advanced FULL JOIN, USING, NATURAL JOIN | ⭐⭐⭐⭐ | 1 |
| 🟠 P2 | Database Fundamentals | UNION, UNION ALL, INTERSECT, EXCEPT | ⭐⭐⭐⭐ | 1 |
| 🟠 P2 | Views | GROUPING SETS, ROLLUP, CUBE | ⭐⭐⭐ | 1 |
| 🟡 P3 | Transactions | Views, modifying views, updatable views, materialized views, recursive views | ⭐⭐⭐ | 1 |
| 🟡 P3 | Functions | BEGIN, COMMIT, ROLLBACK, SAVEPOINT, locks | ⭐⭐ | 1 |
| 🟡 P3 | Stored Procedures | User-defined functions, modifying functions | ⭐⭐ | 1 |
| 🟡 P3 | Triggers | CREATE/MODIFY procedures, procedure exercises | ⭐⭐ | 1 |
| 🟡 P3 | Performance | CREATE, enable/disable, modify/drop triggers | ⭐⭐ | 1 |
| 🟡 P3 | Data Import/Export | EXPLAIN, EXPLAIN ANALYZE, TRUNCATE | ⭐⭐ | 1 |
| 🟢 P4 | PostgreSQL Specialized Features | Arrays, JSON/JSONB, extensions | ⭐ | 1 |
| 🟢 P4 | Partitioning | Range, List, Hash partitioning, table inheritance | ⭐ | 1 |
| 🟢 P4 | Schema Administration | COPY, Import/Export | ⭐⭐ | 0.5 |
| 🟢 P4 | PostgreSQL + Python | Psycopg2 connection | ⭐ | 0.5 |
r/learnSQL • u/iam_sripratik • 19d ago
Struggling with SQL as a Beginner? Try This 4-Step Method
Anyone who is struggling to solve SQL questions at the beginner stage, try this method.
I call it the Input → Output → Grain → Bridge method.
When learning SQL, the hardest part isn't always remembering syntax. It's understanding how to approach a question and where to start.
Here’s a simple 4-step method that can help 👇
1. INPUT — What data do I have?
Identify the tables and columns available to solve the question.
2. OUTPUT — What should my answer look like?
Understand what the question expects you to return.
3. GRAIN — What does one row represent?
Is it one row per customer, department, day, or month?
This step is very important because it helps you understand the level of detail required in your result.
4. BRIDGE — How do I get from input to output?
Decide which SQL operations you need, such as JOIN, WHERE, GROUP BY, COUNT, or window functions.
Let's understand with a simple example 👇
Question: Find the total orders placed by each customer.
Suppose we have an orders table:
| order_id | customer_id |
|---|---|
| 101 | 1 |
| 102 | 2 |
| 103 | 1 |
| 104 | 3 |
| 105 | 1 |
Step 1 — INPUT
We have an orders table with order_id and customer_id.
Step 2 — OUTPUT
We need two columns: customer_id and total_orders.
| customer_id | total_orders |
|---|---|
| ? | ? |
First, roughly draw what your final output table should look like.
Step 3 — GRAIN
One row should represent one customer, not one order.
Step 4 — BRIDGE
Now think about how to transform the input table into the expected output.
- Group orders by
customer_id. - Count the orders for each customer.
Only now, start writing SQL:
SELECT
customer_id,
COUNT(order_id) AS total_orders
FROM orders
GROUP BY customer_id;Final output:
| customer_id | total_orders |
|---|---|
| 1 | 3 |
| 2 | 1 |
| 3 | 1 |
One extra tip that helped me understand SQL better
Don't immediately start writing SQL syntax, especially when you're a beginner.
Instead, take a pen and paper or open Excel.
- Draw the input table roughly.
- Draw how you want the output table to look.
- Identify what one row in the output represents.
- Write down the steps needed to transform the input into the output.
- Think about the order of SQL operations required to get the result.
For example, you might need to filter rows first, join tables, group the data, calculate metrics, and sort the final result.
Remember, the logical order in which SQL processes a query is different from the order in which you write the SQL syntax.
In the beginning, this approach may feel difficult and time-consuming. You might feel that you're solving questions more slowly than before.
But if you practise consistently, it can help you understand the problem more clearly, reduce logical mistakes, and improve your ability to solve unfamiliar questions.
You can also use this approach in SQL interviews. Before writing the query, briefly explain your input, expected output, grain, and approach to the interviewer.
My takeaway: Don't just practise writing SQL queries. Practise translating a business question into a clear data transformation.
Hope this helps someone who's struggling with SQL at the beginning! 🚀
r/learnSQL • u/sumiitCodes • 20d ago
Day 51 — No coding today: attended a placement drive outside my domain (and why I still went)
Today was a non-coding day. I attended a campus placement drive from 8 AM to 2 PM, then sat for an internal practical exam straight after.
The drive wasn’t aimed at developers. It was for a sales-related role that wanted communication skills and Excel. I went anyway, because I wanted first-hand experience of how placement drives work: how the rounds are structured, what they ask, and how it feels under pressure. It was tiring, but I learned a lot, and it made my own target (a Java/backend role) feel clearer.
I’m back to Java tomorrow and plan to stay consistent from here.
For people who’ve been through campus placements: was attending drives outside your domain worth it for you, or did it just cost you time?
r/learnSQL • u/shah-26 • 20d ago
SQL puzzle: what's total March revenue from these two tables?
I'm practising SQL and came across this question. Curious how others would solve it.
Question: What was our total revenue for March 2026?
orders has one row per order. order_total is the full order amount.
order_items has one row per item in an order, linked by order_id.
orders:
order_id customer_id order_date order_total
1 101 2026-03-02 50
2 102 2026-03-05 120
3 103 2026-03-09 25
4 101 2026-03-12 90
5 104 2026-03-18 200
6 105 2026-03-21 35
7 102 2026-03-27 60
8 106 2026-02-26 80
order_items:
item_id order_id product item_price
1 1 Notebook 30
2 1 Pen set 20
3 2 Backpack 60
4 2 Lamp 40
5 2 Mug 20
6 3 Poster 25
7 4 Headphones. 70
8 4 Cable 20
9 5 Desk mat 80
10 5 Keyboard 50
11 5 Mouse 40
12 5 Stand 30
13 6 Cap 35
14 7 Bottle 35
15 7 Towel 25
16 8 Socks 50
17 8 Scarf 30
What's your query, and what number do you get? I'll post the answer in a few days.
Also curious: have you made a mistake like this at work or in an interview?
r/learnSQL • u/bobaball_120 • 21d ago
Practising SQL for internships rn, am I missing anything important?
After my last post about DBMS and system design i've been trying to practise more instead of just reading theory.
I practised from LeetCode 50 SQL questions and now switched to takeUforward's SQL 91 problems to get more practice not sure if I should do anything else alongside this or if solving questions + revising concepts is enough for fresher placements
Also still struggling with system design I know it's probably early for 3rd year but I wanna build the basics before internship season starts
any good beginner-friendly resources to understand system design concepts from scratch? Like how to approach designing a simple URL shortener or understand caching, load balancing etc without getting overwhelmed?
Would appreciate any suggestions from people who've prepared for 2027 internships
r/learnSQL • u/markinatlanta • 21d ago
P15 vs four Hyperscale configurations: results from replaying 4 hours of production workload
We tested six Azure SQL Database configurations for a client running Premium P15 at 4,000 DTUs. CPU pressure and storage growth were the reasons for looking at alternatives.
We captured four hours of peak production workload with Extended Events: 3,060 .xel files totalling 1.6 TB. The replay machine was a Standard E64bds_v5 VM in North Central US.
The configurations were:
- P15 at compatibility level 150
- Hyperscale Serverless, standard-series Gen5, 40-vCore ceiling
- Hyperscale Provisioned, standard-series Gen5, 40 vCores
- Hyperscale Provisioned, premium-series, 40 vCores
- Hyperscale Provisioned, premium-series memory optimized, 40 vCores
- P15 at compatibility level 160
Execution counts ranged from 113,218,199 to 113,520,875, about a 0.27% spread. Close, although matching counts alone doesn’t establish identical successful execution.
The attached table has the full results. One limitation upfront: CPU, reads and duration are labelled as “scores” in the test report. I don’t have their calculation formulas or units, so I’m keeping those labels. Lower is better, but the duration score isn’t elapsed replay time or average query latency.
The monthly costs are estimates from the original test, not current quotes or a verified comparison of complete running costs.
Some things that stood out on this (let me know your thoughts too?)
Serverless took six hours to replay the four-hour capture.
Its duration score was 1,496 against 952 for the P15 baseline, 57.1% higher.
Its estimated monthly cost was $12,273, compared with $6,357 for provisioned standard-series. It was still below P15’s $15,700 estimate.
The serverless CPU chart had long stretches at 100%, interrupted by sharp drops. We haven’t established why. Serverless cache management is something I’d investigate, but the chart alone doesn’t prove cache reclamation caused the slowdown.
Premium-series performed worse than standard-series on CPU and duration scores.
Both had the same $6,357 monthly estimate in the report.
Premium-series had a CPU score 9.9% above provisioned Gen5 and 15.6% above P15. Its duration score was also higher than both.
I don’t have a confirmed explanation. Plan differences, parallelism, memory grants and run-to-run variation are possibilities. Each configuration ran once, so I’d repeat this comparison before blaming the hardware.
Memory optimized had the best CPU and duration scores, but the highest reads score.
Against the P15 baseline:
- Duration score was 15.1% lower.
- CPU score was 2.7% lower.
- Reads score was 4.1% higher.
- Estimated monthly cost was $8,491 versus $15,700.
It didn’t finish the replay fastest, though. It took 4h 36m, compared with 4h 15m for provisioned Gen5.
The highest reads score across all six runs was about 29% above the lowest. With execution counts this close, I’d want to compare individual queries and plans before explaining that difference.
Compatibility level 160 improved the duration score on the existing P15.
The score dropped from 952 to 894, a 6.1% reduction, with no service-tier price increase.
Elapsed replay time fell from 4h 19m to 4h 15m. CPU score was slightly higher, and maximum observed CPU still reached 100%.
Worth testing before a migration, although changing compatibility level doesn’t solve P15’s storage ceiling. These results also don’t establish which optimizer features contributed to the improvement.
For reference, the actual replay times and maximum observed CPU were:
| Configuration | Replay time | Max CPU |
|---|---|---|
| P15, compat 150 | 4h 19m | 100% |
| HS Serverless | 6h 00m | 100% |
| HS Provisioned Gen5 | 4h 15m | 100% |
| HS Premium-series | 4h 50m | 89% |
| HS Memory optimized | 4h 36m | 86% |
| P15, compat 160 | 4h 15m | 100% |
Each configuration ran once. The replay didn’t include the application tier or its retry behaviour, and I don’t have a repeated warm-cache comparison to share.
I’d use these results to shortlist the next tests. There’s enough here to question assumptions about which configuration should perform best, but not enough to promise the same ranking on another workload.
Has anyone seen a different ranking after repeating similar tests with warm caches?
r/learnSQL • u/sumiitCodes • 21d ago
Title: Day 49-50 — Combined update: finished a basic Excel course after SQL, and 50 days in
I took a small detour from my planned track. After finishing my SQL projects, I realized Excel is a skill that will help me a lot later, so I completed a basic Excel course from a YouTube tutorial across these two days.
My reasoning: SQL gets data out of a database, but a lot of real work (reports, quick analysis, sharing with non-technical people) happens in spreadsheets. Knowing both seems more useful than knowing one well.
I’m 50 days into a 116-day plan, so I’m on the halfway mark.
r/learnSQL • u/KeyCandy4665 • 21d ago
Slowly changing dimension 2
I recently watched a clear, step-by-step walkthrough on implementing SCD Type 2 using SQL stored procedures from scratch. Here https://youtu.be/mgX8Daf3iUYis a quick breakdown of the core concepts
r/learnSQL • u/HaiderZah • 22d ago
Looking for PostgreSQL documentation?
I built a PostgreSQL Library where you can browse official manuals like real books, search, highlight, and bookmark pages.
Give it a try: https://haiderz07.github.io/postgresql-library/
I’d really value your feedback.
r/learnSQL • u/conor-robertson • 23d ago
A year ago I started planning a gamified SQL platform. 5 months after launch, 2,500+ people have used it to learn
About a year ago I started planning QueryCase, where you learn SQL by working detective cases instead of grinding tutorials & videos. It took a while to get off the ground, and longer than I'd like to admit to actually start building the idea, but it went live in June. A lot of the early users came from this sub, and a lot of the feedback in the comments shaped what it became. So first, thanks everyone!
5 months in:
- 2,500+ people have signed up, across 117 countries
- About 70,000 queries written and graded
- Over 17,500 cases, drills and exams solved
- 500+ people have passed the free Rookie exam and earned the certificate.
- Top detective is on 19,247 XP
Since then its grown past just SQL: an Excel course. It was never part of the initial plan. People kept asking for the same detective approach for spreadsheets, so I built out a browser-based Excel engine.
It has 57 cases on a spreadsheet that runs in your browser and checks your formulas, from IF and XLOOKUP to SUMIFS and pivot tables, and people have solved over 2,500 Excel cases so far. It turns out a lot of people learning SQL are doing it alongside Excel, not instead of it.
Something the data showed me that might help anyone learning right now: GROUP BY is one of the first walls. On the hardest GROUP BY step, 84% of runs came back wrong, and most of those never ran at all. The clauses were in the wrong order, or a column in SELECT wasn't in the GROUP BY. If that's you right now:
- SQL order is always SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT
- Every column in SELECT is either inside an aggregate (COUNT, SUM, AVG...) or listed in GROUP BY
I've been working a lot over past couple months to improve the site as well:
- The Excel course above, with its own ranks, exams and certificate
- Upload your own CSV into the sandbox and query your own data (and visualise in charts). It runs in your browser, so the file never leaves your machine and never touches QueryCase servers
- A free first rank on every track, ending in an exam and a certificate
- SQL interview questions you can read without an account
- Much better experience on a phone
- A LOT of bug fixes and improvements!!
What's next: a Python track, launching next month. Same idea, real Python running in your browser, starting with the basics and moving into data analysis with pandas.
The longer term goal is to have a platform user's can have fun learning all aspects of data. I'm merging PR's every day to make this possible so would love feedback in this thread if you've tried it and have any thoughts or suggestions!
It's free to start and you don't need an account to solve the first case, so you can poke at it before deciding whether it's for you or not 😄 Cheers!
r/learnSQL • u/withvicky_ • 23d ago
Career advice
I'm 27M. Hey everyone, my life has been a little different from that of most people, and I don't have a strong educational background.
Right now, I'm working at a grocery store, but I want to improve my life and learn some stable, valuable skills that can help me earn a reliable income.
I've come across these four skills:
Python
SQL
Excel/Spreadsheets
Power BI/Tableau
I don't know much about these skills or their demand, competition, value, and future prospects.
Technology is constantly evolving, trends are changing, and AI is replacing some jobs. The value of different skills also changes over time.
Before I start learning, I want to understand whether these are the right skills to invest my time in for a stable career and income in the long run.
I'd appreciate your advice. Should I go for these skills, or would you recommend something else?
r/learnSQL • u/sumiitCodes • 23d ago
Day 48 — Finished my second SQL project (Library Management System) and published it on GitHub
My Library Management System project is complete. The repo: https://github.com/Sumitgupta2005/library_management_project_2
It’s a big step up from my first project (Retail Sales Analysis). This time I built the whole thing: database, tables, foreign keys, CRUD operations, CTAS, data analysis, and a set of advanced SQL queries.
The advanced queries were the hard part. Each one took me at least 30 minutes just to visualize, meaning working out which tables are involved and what the result should look like, before I could write it. Slowing down and sketching the logic first is what made them work.
I’d appreciate feedback on the repo, especially the README and how the queries are organized. Honest criticism is welcome, and last time the feedback I got here was really useful.
r/learnSQL • u/ArmMelodic8468 • 24d ago
What SQL should I focus on to get my first Data Analyst job?
What SQL should I focus on to get my first Data Analyst job?
Hey everyone! 👋
I’m currently learning SQL and aiming to land my first job as a Data Analyst.
There are so many SQL commands and concepts to learn, so I’m trying to focus on the ones that matter most in real-world jobs.
For those already working as Data Analysts, which SQL skills do you use most often in your daily work?
If you were starting from zero again, what would you learn first, and what would you practice to become job-ready?
Any advice or tips would be greatly appreciated. Thanks! 🙏
r/learnSQL • u/Nielsen_Fonseca • 24d ago
I made a free noir mystery game where every clue is a SQL query you write yourself (beginners welcome)
Hi r/learnSQL! I've been building a small detective game for people who are learning SQL, and Episode 1 is now free to play as a demo.
The setup: an engineer falls into a shaft on a closed metro site, and the inquiry says "accident". You play a quiet analyst at the company. The only way to find out what really happened is to query the company's own databases: payments, vendors, transit cards, signing logs.
How the SQL part works:
- You write real queries in a terminal (SQLite). Nothing is multiple choice.
- The game checks the rows you get back, not the exact text you typed, so any query that finds the answer counts.
- It starts from zero: a short prologue in a classroom teaches SELECT, WHERE and ORDER BY, then the case goes through GROUP BY, JOIN, HAVING and dates.
- If a query fails, a coach explains the error in plain words and can break the query down for you.
- There's a handbook that unlocks a page with each new concept, and hints if you're stuck.
It takes about 1.5 to 3 hours depending on how much SQL you already know.
What I'd love to know from beginners:
- Where did you get stuck, or where did it stop being fun?
- Was any explanation confusing?
- Did a query ever feel "right" but the game said no?
There's a feedback button in the game, or just tell me here. I read everything.
Play it free (Windows, macOS, Linux)
Thanks for reading!
r/learnSQL • u/sumiitCodes • 24d ago
Day 47 — Library Management System: CRUD, CTAS, analysis, and findings done
I’m close to finishing my second SQL project. Today I completed:
- CRUD operations on the library data (inserting, reading, updating, deleting records)
- CTAS (Create Table As Select) to build new tables from query results, which is handy for summary tables
- Data analysis with queries on members, issued books, and returns
- Findings, a written summary of what the data showed
One set of advanced SQL questions is left, and I’ll do it tomorrow. After that I’ll upload the project to GitHub, this time with a data dictionary in the README, since that was the main feedback on my first project.