This is the best video explanation I've come across so far that helps me understand not only the difference between NOT IN and NOT EXISTS, but also EXISTS more broadly. Thank you!
Awesome explanation madam, really appriciate your videos... I was banging my head why (NOT IN) operator is not woring as expected.. now after watching your video I know why.
Thank you for another usefull video. I have a question - there is any difference when we make a inner join comparing with a join on exists not where having a 1 to many relationship? Thank you
Hi, how to fix this. After creating a table, I can't see where the table is?Before I had the success of creating a table but now i can't see the table after creating the table, Thank you
Very few columns should have NULL values and if you are having to do special coding consideration for a NULL column then you have a bad database design. If you have a NOT you might want to consider making a temp table and then joining that temp table rather than doing a NOT EXISTS or NOT IN. Better definition is that EXISTS should be used when you have a ONE-to-ONE relationship and IN where you have something in a collection.
@@filipzivkovic4866 Hi bro plz tell : where is less Work load , less work Pressure & less Working Hrs. - as a Data Analyst or as Machine learning Engineer or as a Data Scientists ?
This is the best video explanation I've come across so far that helps me understand not only the difference between NOT IN and NOT EXISTS, but also EXISTS more broadly. Thank you!
Glad it was helpful!
Awesome explanation madam, really appriciate your videos... I was banging my head why (NOT IN) operator is not woring as expected.. now after watching your video I know why.
Glad it was helpful.
Amazing, Thank you.
Thank you, this was really helpful.
This video is very handy, corelated subquery and where conditions.
Thank You!
Interesting concept of null comparison in SQL. Thank you!
Thank you
Very informative
Nice explanation...👍
Thank you
Thank you for another usefull video.
I have a question - there is any difference when we make a inner join comparing with a join on exists not where having a 1 to many relationship?
Thank you
Hi, how to fix this. After creating a table, I can't see where the table is?Before I had the success of creating a table but now i can't see the table after creating the table, Thank you
What is difference between IN Operator and EXISTS Operator ?Which is Faster? can you make it video on this
Very few columns should have NULL values and if you are having to do special coding consideration for a NULL column then you have a bad database design. If you have a NOT you might want to consider making a temp table and then joining that temp table rather than doing a NOT EXISTS or NOT IN. Better definition is that EXISTS should be used when you have a ONE-to-ONE relationship and IN where you have something in a collection.
please provide the create and insert table scripts this will help everyone
-- dbo.Employee table
create table dbo.TblEmployee
(
EmpID INT not null PRIMARY KEY,
DeptID INT not null,
SubDeptID NCHAR (10)
)
-- Inserted values
INSERT into dbo.TblEmployee (EmpID, DeptID, SubDeptID)
VALUES
(1001,1,'A'),
(1002,2,'X'),
(1003,3,'A'),
(1004,4,'A'),
(1005,5,'A')
-- dbo.TblDept
create table dbo.TblDept
(
DeptID INT not null IDENTITY(1,1) PRIMARY KEY,
SubDeptID NCHAR(10) not null
)
-- Inserted values
insert into dbo.TblDept (SubDeptID)
VALUES
('A'),
('A'),
('B'),
('A')
My bad, I forgot to add the NULL in the TblDept table
@@filipzivkovic4866
Hi bro plz tell : where is less Work load , less work Pressure & less Working Hrs. - as a Data Analyst or as Machine learning Engineer or as a Data Scientists ?
It Should be "............WHERE DEPTID NOT EXISTS............" . can you elaborate more............