Nested select statement in SQL Server

sql

subqueries

data-aggregation

query-optimization

byAlex Kataev·Sep 9, 2024

Using nested SELECTs is a great way to level-up your SQL skills. These come into play when you need to fetch data based on conditions referencing multiple tables or complex data manipulations. Let's say we need to fetch employees who are also managers:

SELECT *
FROM Employees
WHERE EmployeeID IN (SELECT ManagerID FROM Departments);

Within the WHERE clause, SELECT ManagerID FROM Departments is a subquery acting as a filter for the Employees. Ensure that subqueries return a single column when using operators like IN. Also, keep the nesting to a minimum to maintain query performance.

Naming your subqueries

When dealing with subqueries, it's best to assign an alias for cleaner referencing and readability:

SELECT a.name
FROM (SELECT name FROM agentinformation) AS a;

Here we name the subquery (SELECT name FROM agentinformation) as a using the AS clause. This essentially forms a derived table which enhances query readability.

Multiple faces of subqueries

Subqueries take many forms and each serve a particular purpose:

IN checks if a value exists in the subquery's return set.
NOT IN filters out values present in the subquery's results.
ANY and ALL perform a comparison against each value returned by the subquery.
EXISTS checks the existence of any subquery results.

Understanding these alternatives will help you handle a broad array of data fetching scenarios.

Cleanup on aisle order

Subqueries can also assist with data aggregation and sorting order:

SELECT Name, (SELECT COUNT(*) FROM Orders o WHERE o.CustomerID = c.CustomerID) AS TotalOrders
FROM Customers c
ORDER BY TotalOrders DESC;

Here, the subquery is counting orders for each customer. Meanwhile, the main query is arranging customers based on this count. Remember, an organized data is a happy data.

Performance and complexity management

Adding more floors (subqueries) increases complexity and resource demand. Remember to:

Have indexes on fields used in join conditions and where clauses within subqueries.
Utilize SQL Server's execution plans for query optimization.
Consider using Common Table Expressions (CTEs) or temporary tables for complex operations, because simplification is the ultimate sophistication.

Advanced maneuver: Correlated subqueries

Correlated subqueries bring in an added level of complexity where each subquery is dependent on the outer query for values:

SELECT e.Name,
       (SELECT TOP 1 Salary FROM Salaries s WHERE s.EmployeeID = e.EmployeeID ORDER BY s.Date DESC) AS CurrentSalary
FROM Employees e;

In this example, Salary Romance is happening - a peek at the most recent salary for each employee is obtained through the intimate correlation between the inner and outer query.

explain-codes / Sql / Nested select statement in SQL Server

Linked

How can I delete using INNER JOIN with SQL Server?



Subquery in FROM must have an alias



Select * from subquery



Sql - using alias in Group By



Using an Alias in a WHERE clause

