Foreign Key (FK) Constraint in SQL Server (Referential Integrity in DBMS)

preview_player
Показать описание
#ForeignKey (FK) Constraint in SQL Server & #ReferentialIntegrity in DBMS

#SQLwithManoj

Рекомендации по теме
Комментарии
Автор

THANKS MANOJ YOU'RE A SUPER STAR MATE YOU MADE SQL SERVER A PIECE OF CAKE GOD BLESS YOU

xkhan
Автор

Very thorough demonstration -- thank you!

rogerbreton
Автор

Superb content and explanation Manoj..thanks..Hope u hav covered Cascading update/delete in next videos.

ashok
Автор

A foreign key must be either wholly null or exist as a primary key in another table
(This statement is true for the refrential constraint) ??

ammadmaddy
Автор

Hello manoj can you explain that why we use dbo, Employee.My Question is why you use dbo. with table name .

ajaytawaniya
Автор

AND ALSO DO YOU HAVE VIDEOS ABOUT DATA WAREHOUSING AND T-SQL??PLEASE LET US KNOW
KIND REGARDS
KHIZER

xkhan
Автор

Hi Manoj, in the table for Employee, the dept_id_fk appears to be defaulted to NULL. Is it because that such employees does not have department associated yet? Is such feature allowed in SQL Server? How about Oracle if you have an idea? Thanks in advance.

HussainMohammedAshruf
Автор

Thanks for a nice tutorial on the FK. but i can't understand this type of insert statement.
INSERT INTO Department (DepartmentName)
SELECT 'HR'
UNION ALL
SELECT 'Finance'
UNION ALL
SELECT 'Admin'
UNION ALL
SELECT 'IT'
UNION ALL
it is a bit unique to me, could you please explain this a little. Tthanks!

mettleUnbeaten