#30daysofsql 搜尋結果

未找到 "#30daysofsql" 的結果

Day 27 of my #30DaysOfSQL Stored Procedures vs Functions, finally making sense. Today I focused on SQL Functions, and they were confusing at first. The breakthrough came when I understood this simple idea: Stored procedures PERFORM tasks. Functions RETURN results.

iam_AruCole's tweet image. Day 27 of my #30DaysOfSQL Stored Procedures vs Functions, finally making sense.

Today I focused on SQL Functions, and they were confusing at first. The breakthrough came when I understood this simple idea:

Stored procedures PERFORM tasks.
Functions RETURN results.
iam_AruCole's tweet image. Day 27 of my #30DaysOfSQL Stored Procedures vs Functions, finally making sense.

Today I focused on SQL Functions, and they were confusing at first. The breakthrough came when I understood this simple idea:

Stored procedures PERFORM tasks.
Functions RETURN results.
iam_AruCole's tweet image. Day 27 of my #30DaysOfSQL Stored Procedures vs Functions, finally making sense.

Today I focused on SQL Functions, and they were confusing at first. The breakthrough came when I understood this simple idea:

Stored procedures PERFORM tasks.
Functions RETURN results.
iam_AruCole's tweet image. Day 27 of my #30DaysOfSQL Stored Procedures vs Functions, finally making sense.

Today I focused on SQL Functions, and they were confusing at first. The breakthrough came when I understood this simple idea:

Stored procedures PERFORM tasks.
Functions RETURN results.

DAY 13 of my SQL Journey Today is about learning window functions row_number(), rank() and how partition by works. It was a bit confusing at first but with some examples I tried it started making sense. Slowly getting there. #30DaysOfSQL #DataAnalytics

Stacierealm's tweet image. DAY 13 of my SQL Journey 

Today is about learning window functions row_number(), rank() and how partition by works. It was a bit confusing at first but with some examples I tried it started making sense.
Slowly getting there.

#30DaysOfSQL #DataAnalytics

Day 26 of #30DaysOfSQL CTEs just made SQL make sense Today I learned how Common Table Expressions (CTEs) break complex logic into simple, readable steps. Instead of stuffing everything into one massive query, a CTE lets you think in layers.

iam_AruCole's tweet image. Day 26 of #30DaysOfSQL CTEs just made SQL make sense 

Today I learned how Common Table Expressions (CTEs) break complex logic into simple, readable steps.

Instead of stuffing everything into one massive query, a CTE lets you think in layers.
iam_AruCole's tweet image. Day 26 of #30DaysOfSQL CTEs just made SQL make sense 

Today I learned how Common Table Expressions (CTEs) break complex logic into simple, readable steps.

Instead of stuffing everything into one massive query, a CTE lets you think in layers.
iam_AruCole's tweet image. Day 26 of #30DaysOfSQL CTEs just made SQL make sense 

Today I learned how Common Table Expressions (CTEs) break complex logic into simple, readable steps.

Instead of stuffing everything into one massive query, a CTE lets you think in layers.

Day 10/30 Today was all about string functions left, substring, replace, charindex e.t.c . These functions are powerful for cleaning, formatting, and preparing data for analysis. Which SQL function do you think is underrated but super useful? #30DaysOfSQL #buildinginpublic

Stacierealm's tweet image. Day 10/30
Today was all about string functions left, substring, replace, charindex e.t.c . These functions are  powerful for cleaning, formatting, and preparing data for analysis.

Which SQL function do you think is underrated but super useful?
#30DaysOfSQL #buildinginpublic
Stacierealm's tweet image. Day 10/30
Today was all about string functions left, substring, replace, charindex e.t.c . These functions are  powerful for cleaning, formatting, and preparing data for analysis.

Which SQL function do you think is underrated but super useful?
#30DaysOfSQL #buildinginpublic

Day 25 of #30DaysOfSQL I learned how powerful PARTITION BY is in SQL Server. Unlike GROUP BY, it keeps all rows while adding totals and insights. Example: show each employee’s salary + total salary of their department

iam_AruCole's tweet image. Day 25 of #30DaysOfSQL
I learned how powerful PARTITION BY is in SQL Server.
Unlike GROUP BY, it keeps all rows while adding totals and insights.
Example: show each employee’s salary + total salary of their department
iam_AruCole's tweet image. Day 25 of #30DaysOfSQL
I learned how powerful PARTITION BY is in SQL Server.
Unlike GROUP BY, it keeps all rows while adding totals and insights.
Example: show each employee’s salary + total salary of their department

Day 23 of #30DaysOfSQL Today I learned about Views in SQL Server and honestly, this feels like a mini superpower. A View is basically a saved SQL query that behaves like a virtual table. It makes your work cleaner, faster, and more consistent.

iam_AruCole's tweet image. Day 23 of #30DaysOfSQL
Today I learned about Views in SQL Server and honestly, this feels like a mini superpower.

A View is basically a saved SQL query that behaves like a virtual table.
It makes your work cleaner, faster, and more consistent.
iam_AruCole's tweet image. Day 23 of #30DaysOfSQL
Today I learned about Views in SQL Server and honestly, this feels like a mini superpower.

A View is basically a saved SQL query that behaves like a virtual table.
It makes your work cleaner, faster, and more consistent.

Day 9 of my SQL Journey 💻 Hi #datafam, so today I decided to face my subquery fear and I started getting the hang of it. Subquery makes breaking down complex queries less scary What’s your favorite SQL trick for handling tricky queries? #30DaysOfSQL #Buildinginpublic

Stacierealm's tweet image. Day 9 of my SQL Journey 💻
Hi #datafam, so today I decided to face my subquery fear and I started getting the hang of it. Subquery makes breaking  down complex queries less scary 

What’s your favorite SQL trick for handling tricky queries?

#30DaysOfSQL #Buildinginpublic

I’m starting #30DaysOfSQL today! 💪 For the next 30 days, I’ll share 1 SQL concept daily — from basics to advanced. Short. Practical. Easy to learn. Follow along and bookmark this thread 👇 Let’s make SQL fun again! 💙 #SQL #DataAnalytics #DataScience #LearnSQL


🧵 Day 1 of my #30DaysOfSQL Journey Today I learned “Introduction to Databases & SQL.” A database = organized collection of data. SQL (Structured Query Language) = the language used to talk to databases.


I’ll be sharing daily progress, resources, and lessons learned along the way. If you’re learning SQL too, let’s connect and grow together!✍️🫡 #SQL #DataAnalytics #30DaysOfSQL


Day 22 of #30DaysOfSQL Understanding Indexes in SQL Server ⚡ Indexes make queries faster by helping SQL Server find data without scanning the whole table. Think of an index as a table of contents for your data. 🧵

iam_AruCole's tweet image. Day 22 of #30DaysOfSQL Understanding Indexes in SQL Server ⚡

Indexes make queries faster by helping SQL Server find data without scanning the whole table.

Think of an index as a table of contents for your data. 🧵
iam_AruCole's tweet image. Day 22 of #30DaysOfSQL Understanding Indexes in SQL Server ⚡

Indexes make queries faster by helping SQL Server find data without scanning the whole table.

Think of an index as a table of contents for your data. 🧵
iam_AruCole's tweet image. Day 22 of #30DaysOfSQL Understanding Indexes in SQL Server ⚡

Indexes make queries faster by helping SQL Server find data without scanning the whole table.

Think of an index as a table of contents for your data. 🧵
iam_AruCole's tweet image. Day 22 of #30DaysOfSQL Understanding Indexes in SQL Server ⚡

Indexes make queries faster by helping SQL Server find data without scanning the whole table.

Think of an index as a table of contents for your data. 🧵

Day 21 of #30DaysOfSQL Nested Joins + Subqueries in Joins (SQL Server Edition) I’ve joined 2 tables before, now let’s link 3 or 4+ 💪🧵

iam_AruCole's tweet image. Day 21 of #30DaysOfSQL
Nested Joins + Subqueries in Joins (SQL Server Edition)

I’ve joined 2 tables before, now let’s link 3 or 4+ 💪🧵
iam_AruCole's tweet image. Day 21 of #30DaysOfSQL
Nested Joins + Subqueries in Joins (SQL Server Edition)

I’ve joined 2 tables before, now let’s link 3 or 4+ 💪🧵
iam_AruCole's tweet image. Day 21 of #30DaysOfSQL
Nested Joins + Subqueries in Joins (SQL Server Edition)

I’ve joined 2 tables before, now let’s link 3 or 4+ 💪🧵
iam_AruCole's tweet image. Day 21 of #30DaysOfSQL
Nested Joins + Subqueries in Joins (SQL Server Edition)

I’ve joined 2 tables before, now let’s link 3 or 4+ 💪🧵

Little win in my #30DaysOfSQL journey: I just switched from MySQL → SQL Server & wow, I see the flavours of SQL clearly now. ✅ MySQL: simple, great start ✅ SQL Server: richer (INTERSECT, EXCEPT, CTEs, window funcs) Even small syntax shifts = big growth. Loving it! #sql

iam_AruCole's tweet image. Little win in my #30DaysOfSQL journey:

I just switched from MySQL → SQL Server & wow, I see the flavours of SQL clearly now.

✅ MySQL: simple, great start
✅ SQL Server: richer (INTERSECT, EXCEPT, CTEs, window funcs)

Even small syntax shifts = big growth. Loving it!
#sql

Rules to remember: Both queries must return the same number of columns Data types must be compatible #30DaysOfSQL #SQLServer #LearningInPublic

iam_AruCole's tweet image. Rules to remember:

Both queries must return the same number of columns

Data types must be compatible

#30DaysOfSQL #SQLServer #LearningInPublic
iam_AruCole's tweet image. Rules to remember:

Both queries must return the same number of columns

Data types must be compatible

#30DaysOfSQL #SQLServer #LearningInPublic
iam_AruCole's tweet image. Rules to remember:

Both queries must return the same number of columns

Data types must be compatible

#30DaysOfSQL #SQLServer #LearningInPublic
iam_AruCole's tweet image. Rules to remember:

Both queries must return the same number of columns

Data types must be compatible

#30DaysOfSQL #SQLServer #LearningInPublic

Day 20 of #30DaysOfSQL Set Operators in SQL Server Sometimes, you need to compare results from 2 queries. Instead of joins, SQL gives us Set Operators Let’s break them down 🧵

iam_AruCole's tweet image. Day 20 of #30DaysOfSQL  Set Operators in SQL Server

Sometimes, you need to compare results from 2 queries. Instead of joins, SQL gives us Set Operators 

Let’s break them down 🧵
iam_AruCole's tweet image. Day 20 of #30DaysOfSQL  Set Operators in SQL Server

Sometimes, you need to compare results from 2 queries. Instead of joins, SQL gives us Set Operators 

Let’s break them down 🧵
iam_AruCole's tweet image. Day 20 of #30DaysOfSQL  Set Operators in SQL Server

Sometimes, you need to compare results from 2 queries. Instead of joins, SQL gives us Set Operators 

Let’s break them down 🧵
iam_AruCole's tweet image. Day 20 of #30DaysOfSQL  Set Operators in SQL Server

Sometimes, you need to compare results from 2 queries. Instead of joins, SQL gives us Set Operators 

Let’s break them down 🧵

Hi everyone, here's the link to the project I created for the #30DaysOfSQL challenge. I'd love your thoughts and feedback. Thank you for engaging. github.com/Elizabeth-moyi#learnwithmoyinofcanada #30SQLchallenge #Datacommunity @cheftee_lead @Odunthedatagirl

It's day 30 of my 30 day SQL learning challenge, and it's been quite a journey. From struggling to import datasets into SQL Workbench and facing errors to mastering joins, subqueries, CTEs, and complex SQL functions that challenged my life choices.

Moyinofcanada's tweet image. It's day 30 of my 30 day SQL learning challenge, and it's been quite a journey. From struggling to import datasets into SQL Workbench and facing errors to mastering joins, subqueries, CTEs, and complex SQL functions that challenged my life choices.
Moyinofcanada's tweet image. It's day 30 of my 30 day SQL learning challenge, and it's been quite a journey. From struggling to import datasets into SQL Workbench and facing errors to mastering joins, subqueries, CTEs, and complex SQL functions that challenged my life choices.


Key takeaway: Self-joins let you explore hierarchies within one table. #SQL #30DaysOfSQL #LearningInPublic #DataAnalytics


Day 19 of #30DaysOfSQL Self-Joins Sometimes the data you need is in one table. That’s when we use a Self-Join. 🧵

iam_AruCole's tweet image. Day 19 of #30DaysOfSQL   Self-Joins

Sometimes the data you need is in one table.
 That’s when we use a Self-Join.

🧵
iam_AruCole's tweet image. Day 19 of #30DaysOfSQL   Self-Joins

Sometimes the data you need is in one table.
 That’s when we use a Self-Join.

🧵

Recap: INNER JOIN → only matches LEFT JOIN → all left RIGHT JOIN → all right FULL JOIN → simulate with UNION CROSS JOIN → all combos #SQL #MySQL #30DaysOfSQL #LearningInPublic

iam_AruCole's tweet image. Recap:

INNER JOIN → only matches

LEFT JOIN → all left

RIGHT JOIN → all right

FULL JOIN → simulate with UNION

CROSS JOIN → all combos

#SQL #MySQL #30DaysOfSQL #LearningInPublic

Day 18 of #30DaysOfSQL — FULL JOIN & CROSS JOIN (MySQL) MySQL doesn’t support FULL JOIN directly. But here’s how to handle it 🧵

iam_AruCole's tweet image. Day 18 of #30DaysOfSQL — FULL JOIN & CROSS JOIN (MySQL)

MySQL doesn’t support FULL JOIN directly. But here’s how to handle it 🧵
iam_AruCole's tweet image. Day 18 of #30DaysOfSQL — FULL JOIN & CROSS JOIN (MySQL)

MySQL doesn’t support FULL JOIN directly. But here’s how to handle it 🧵
iam_AruCole's tweet image. Day 18 of #30DaysOfSQL — FULL JOIN & CROSS JOIN (MySQL)

MySQL doesn’t support FULL JOIN directly. But here’s how to handle it 🧵
iam_AruCole's tweet image. Day 18 of #30DaysOfSQL — FULL JOIN & CROSS JOIN (MySQL)

MySQL doesn’t support FULL JOIN directly. But here’s how to handle it 🧵

未找到 "#30daysofsql" 的結果
未找到 "#30daysofsql" 的結果
Loading...

Something went wrong.


Something went wrong.


United States Trends