Skip to main content

Using SQL self join Find Upper level manager in Employee table

A self-join is a query in which a table is joined (compared) to itself. Self-joins are used to compare values in a column with other values in the same column in the same table.
You can use a self-join to simplify nested SQL queries where the inner and outer queries reference the same table. These joins allow you to retrieve related records from the same table. The most common case where you'd use a self-join is when you have a table that references itself

I have the employee detail table, In that i want to find the manager for each Employee.
The employee name and manager column are present in same table
Consider the following Employee table

CREATE TABLE Employee
(
    Emp_Id INT IDENTITY(1,1) NOT NULL PRIMARY KEY,
    Emp_Name VARCHAR(100),
    Manager_Id INT NULL
)

INSERT INTO Employee(Emp_Name,Manager_Id)VALUES('a',null)
INSERT INTO Employee(Emp_Name,Manager_Id)VALUES('b',1)
INSERT INTO Employee(Emp_Name,Manager_Id)VALUES('c',2)
INSERT INTO Employee(Emp_Name,Manager_Id)VALUES('d',3)
INSERT INTO Employee(Emp_Name,Manager_Id)VALUES('e',4)
INSERT INTO Employee(Emp_Name,Manager_Id)VALUES('f',5)

Emp_Id
Emp_Name
Manager_Id
1
a
Null
2
b
1
3
c
2
4
d
3
5
e
4
6
f
5

To find the manager name for each employee in the Employee table

SELECT e2.Emp_Id,
      e2.Emp_Name as EMP_NAME,
      e1.Emp_Name as MANAGER_NAME
FROM Employee e1,Employee e2
WHERE e1.Emp_Id=e2.Manager_Id

OUTPUT
Emp_Id
EMP_NAME
Manager_NAME
2
b
a
3
c
b
4
d
c
5
e
d
6
f
e

Now find the Employee Manager Name and its senior Manager Name

SELECT e2.Emp_Id,
         e2.Emp_Name AS EMP_NAME,
         e1.Emp_Name AS MANAGER_NAME,
         e3.Emp_Name AS SENIOR_MANAGER_NAME
FROM Employee e1, Employee e2, Employee e3
WHERE e1.Emp_Id= e2.Manager_Id
AND e1.Manager_Id = e3.Emp_Id
ORDER BY e2.Emp_Id

OUTPUT

Emp_Id
EMP_NAME
MANAGER_NAME
SENIOR_MANAGER_NAME
3
c
b
a
4
d
c
b
5
e
d
c
6
f
e
d

Comments

  1. Very nice one Rahul, thanks for sharing and taking effort to write this.

    Good page here too:

    How self join works

    ReplyDelete

Post a Comment

Popular posts from this blog

Connected and disconnected architecture in ADO.Net with Example

Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction.  Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a recor

HTTPHandler and HTTPModule in ASP.NET

If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler .   The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension.  For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: -    It's just like a filter. The Modules are called before and after the handler executes . -    HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional services within the pipeline -  

ASP.NET Page Life Cycle with example

In this article, we are going to discuss the different methods and order they are executed during the load of an .aspx web page. Methods Description Page_PreInit Before page Initialization Page_Init Page Initialization LoadViewState View State Loading LoadPostData Postback Data Processing Page_Load Page Loading RaisePostDataChangedEvent PostBack Change Notification RaisePostBackEvent PostBack Event Handling Page_PreRender Page Pre Rendering Phase SaveViewState View State Saving Page_Render Page Rendering Page_Unload Page Unloading PreInit : The entry point of the page life cycle is the pre-initialization phase called “PreInit”. You can dynamically set the values of master pages and themes in this event. You can also dynamically create controls in this event.  Init : This event fires after each control h