Skip to main content

3 Ways of Inner Join

An 'Inner Join' is used to join operation in an applications, which creates a new result table by combining column values of two tables (A and B) based upon the join-predicate. The query compares each row of A with each row of B to find all pairs of rows which satisfy the join-predicate. When the join-predicate is satisfied by matching non-NULL values, column values for each matched pair of rows of A and B are combined into a result row.
We can create inner Join through various method in application. I want to share 3 ways which I used in various application.
  1. Implicit Join Method
  2. Explicit Join Method
  3. Cross Apply Method

Sample Data
CREATE TABLE [Department](
   [DepartmentID] [int] NOT NULL PRIMARY KEY,
   [Name] VARCHAR(250) NOT NULL,
INSERT [Department] ([DepartmentID], [Name]) 
VALUES (1, N'Engineering')
INSERT [Department] ([DepartmentID], [Name]) 
VALUES (2, N'Administration')
INSERT [Department] ([DepartmentID], [Name]) 
VALUES (3, N'Sales')
INSERT [Department] ([DepartmentID], [Name]) 
VALUES (4, N'Marketing')
INSERT [Department] ([DepartmentID], [Name]) 
VALUES (5, N'Finance')
CREATE TABLE [Employee](
   [EmployeeID] [int] NOT NULL PRIMARY KEY,
   [FirstName] VARCHAR(250) NOT NULL,
   [LastName] VARCHAR(250) NOT NULL,
   [DepartmentID] [int] NOT NULL REFERENCES [Department](DepartmentID),
INSERT [Employee] ([EmployeeID], [FirstName], [LastName], [DepartmentID])
VALUES (1, N'Ajay', N'Verma', 1 )
INSERT [Employee] ([EmployeeID], [FirstName], [LastName], [DepartmentID])
VALUES (2, N'Sujit', N'Khanna', 2 )
INSERT [Employee] ([EmployeeID], [FirstName], [LastName], [DepartmentID])
VALUES (3, N'Deelip', N'Jha', 3 )
INSERT [Employee] ([EmployeeID], [FirstName], [LastName], [DepartmentID])
VALUES (4, N'Rajesh', N'Kumar', 3 )

     1.) 1st Method : Implicit Join Notation
SELECT * FROM Department D, Employee E where  D.DepartmentID = E.DepartmentID
     2.) 2nd Method : Explicit Join Notation
SELECT * FROM Department INNER JOIN Employee E ON D.DepartmentID = E.DepartmentID 
3.) 3rd Method : Cross Apply
   SELECT * FROM Employee E
   WHERE E.DepartmentID = D.DepartmentID
   ) A


There will not be any performance changes on any way. All the way will give same performance impact...


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription