-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsubqueries.sql
More file actions
188 lines (149 loc) · 5.13 KB
/
Copy pathsubqueries.sql
File metadata and controls
188 lines (149 loc) · 5.13 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
-- =========================================================
-- FILE: subqueries.sql
-- PROJECT: TechSphere Solutions Database System
-- AUTHOR: Benard Onyango Omoga
-- DESCRIPTION:
-- Demonstrates Subqueries in MySQL using TechSphere schema.
-- Subqueries are queries nested inside other queries and used
-- for filtering, calculations, and derived tables.
-- =========================================================
-- =========================================================
-- USE DATABASE
-- =========================================================
USE techsphere_solutions;
-- =========================================================
-- SECTION 1: INTRODUCTION TO SUBQUERIES
-- PURPOSE:
-- Subqueries allow one query to be embedded inside another query.
-- They are used to return intermediate results for the main query.
-- =========================================================
-- View all employees
SELECT *
FROM employees;
-- =========================================================
-- SECTION 2: SUBQUERY IN WHERE CLAUSE
-- PURPOSE:
-- Filter employees using results from another query
-- =========================================================
SELECT *
FROM employees
WHERE employee_id IN (
SELECT ep.employee_id
FROM employee_positions ep
JOIN job_roles jr
ON ep.role_id = jr.role_id
WHERE jr.role_title = 'Data Analyst'
);
-- WHAT IT DOES:
-- Inner query finds employees with Data Analyst role
-- Outer query returns full employee details
-- Demonstrates filtering using a dynamic list
-- =========================================================
-- SECTION 3: INVALID SUBQUERY EXAMPLE (IMPORTANT RULE)
-- PURPOSE:
-- Show common mistake when using subqueries
-- =========================================================
-- This query would fail:
-- SELECT *
-- FROM employees
-- WHERE employee_id IN (
-- SELECT employee_id, department_id
-- FROM employee_positions
-- );
-- WHAT IT DOES:
-- ERROR occurs because IN expects only ONE column
-- KEY RULE:
-- Subqueries used with IN must return a single column only
-- =========================================================
-- SECTION 4: SUBQUERY IN SELECT CLAUSE
-- PURPOSE:
-- Compare each employee against global salary average
-- =========================================================
SELECT
e.first_name,
e.last_name,
jr.base_salary,
(
SELECT AVG(base_salary)
FROM job_roles
) AS avg_salary
FROM employees e
JOIN employee_positions ep
ON e.employee_id = ep.employee_id
JOIN job_roles jr
ON ep.role_id = jr.role_id;
-- WHAT IT DOES:
-- Displays each employee salary
-- Adds overall average salary (same value for all rows)
-- Useful for benchmarking performance
-- =========================================================
-- SECTION 5: SUBQUERY IN FROM CLAUSE (DERIVED TABLE)
-- PURPOSE:
-- Create temporary aggregated dataset for further querying
-- =========================================================
SELECT *
FROM (
SELECT
d.department_name,
COUNT(e.employee_id) AS total_employees,
AVG(jr.base_salary) AS avg_salary
FROM employees e
JOIN departments d
ON e.department_id = d.department_id
JOIN employee_positions ep
ON e.employee_id = ep.employee_id
JOIN job_roles jr
ON ep.role_id = jr.role_id
GROUP BY d.department_name
) AS dept_summary;
-- WHAT IT DOES:
-- Creates a virtual table (dept_summary)
-- Shows department size and average salary
-- =========================================================
-- SECTION 6: FILTERING DERIVED TABLE (ADVANCED USE)
-- PURPOSE:
-- Apply filtering on aggregated subquery results
-- =========================================================
SELECT department_name, total_employees, avg_salary
FROM (
SELECT
d.department_name,
COUNT(e.employee_id) AS total_employees,
AVG(jr.base_salary) AS avg_salary
FROM employees e
JOIN departments d
ON e.department_id = d.department_id
JOIN employee_positions ep
ON e.employee_id = ep.employee_id
JOIN job_roles jr
ON ep.role_id = jr.role_id
GROUP BY d.department_name
) AS dept_summary
WHERE total_employees > 1
ORDER BY avg_salary DESC;
-- WHAT IT DOES:
-- Filters departments with more than 1 employee
-- Sorts departments by highest average salary
-- =========================================================
-- KEY RULES OF SUBQUERIES
-- =========================================================
-- 1. Subqueries can be used in:
-- WHERE, SELECT, FROM clauses
-- 2. IN subqueries must return ONE column only
-- 3. FROM subqueries must have an alias
-- 4. Subqueries can return:
-- - Single value (scalar)
-- - List of values
-- - Derived table
-- =========================================================
-- BUSINESS USE CASES
-- =========================================================
-- Subqueries are used for:
-- - HR analytics (employee filtering)
-- - Salary benchmarking
-- - Department reporting
-- - KPI calculations
-- - Data aggregation for dashboards
-- =========================================================
-- END OF FILE
-- =========================================================