[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 358
  • Last Modified:

Need help on understanding recursive CTE

Hello,
I am studying recursive CTE and I am having trouble understanding the recursive portion of the cte.  Below is the example.  I want to make sure that I understand what's going on.  I understand the anchor member portion but am not sure how the recursive portion works.  I've read the explanation but am still having trouble with the concept.  I'm studying on my own.

USE Examples;

WITH EmployeesCTE AS
(
		-- Anchor member
		SELECT EmployeeID, 
			FirstName + ' ' + LastName As EmployeeName, 
			1 As Rank
		FROM Employees
		WHERE ManagerID IS NULL
	UNION ALL
		-- Recursive member
		SELECT Employees.EmployeeID, 
			FirstName + ' ' + LastName, 
			Rank + 1
		FROM Employees
			JOIN EmployeesCTE
			ON Employees.ManagerID = EmployeesCTE.EmployeeID
)
SELECT *
FROM EmployeesCTE
ORDER BY Rank, EmployeeID

Open in new window

0
chtullu135
Asked:
chtullu135
  • 5
  • 2
1 Solution
 
chtullu135Author Commented:
I think what is happening is that "Join EmployeesCTE" is referring to the previous pass .
0
 
Kent OlsenData Warehouse Architect / DBACommented:
Hit chtullu135,

There are a couple of articles on the DB2 forum that explain recursive SQL very well.  The only difference between the DB2 and SQL Server variants is how string parameters are sized (it's explained in the articles).  The only other significant difference is that DB2 uses the double pipe (||) for string concatenation and SQL Server uses the plus sign (+).

  http://www.experts-exchange.com/Database/DB2/A_3629-Recursive-SQL-in-DB2-Converting-Columns-to-Rows.html

  http://www.experts-exchange.com/Database/DB2/A_3618-Recursive-SQL-in-DB2-Converting-rows-to-columns.html


Briefly, the upper sub-query in the CTE establishes the starting point of the recursive query.  The lower sub-query in the CTE processes all of the rows (except the first row) and defines when the recursion is complete.


In your query, the upper sub-query selects all employees without a manager.  The lower sub-query doesn't seem to select rows in a meaningful fashion.  What is it trying to do?


Kent
0
 
chtullu135Author Commented:
Hello Kent,
The lower subquery returns each employee according the their level in the organization.  Below is the list of Employee

Empid                                             Managerid
1                Smith      Cindy               NULL
2                Jones      Elmer                 1
3                Simonian      Ralph         2
4               Hernandez      Olivia         9
5               Aaronsen      Robert         4
6               Watson      Denise                 8
7                Hardy      Thomas                2
8      O'Leary      Rhea      9
9      Locario      Paulo      1
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
chtullu135Author Commented:
0
 
Kent OlsenData Warehouse Architect / DBACommented:
Ok.

Using your sample data, the upper sub-query selects the row for Cindy Smith -- the only row with NULL for the manager id.

The lower sub-query takes that row and joins the employees table to it and filters in a way that the employees that are Cindy's direct reports are selected.  (Paulo Locario and Elmer Jones.)

The next iteration selects the rows for people that report to Locario and Jones.

Note that the selections are not linear.  People want to think of recursive SQL as iterating through a list.  In reality, SQL is taking some number of rows of data and generating more rows of data.  (All level 1 rows are generated at the same time, all level 2 rows are generated at the same time, etc.)

The other real gotcha is that ALL of the rows that are generated are part of the final result set.  You may need to filter or sort them differently for your own needs.  In this case, I believe that you'd be well served for the DTE to pass the employeeID and managerID values.


Kent
0
 
chtullu135Author Commented:
Thanks Kent.  My problem was that I was thinking the the recursion was iterating through a list instead of a set of rows.
0
 
chtullu135Author Commented:
Thanks again for your help
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now