How would you add a foreign key constraint on the dept_no column in the EMP table, referring to the id column in the DEPT table?

1. Create a table called EMP with the following structure. Name Type EMPNO NUMBER (6) ENAME VARCHAR2 (20) JOB VARCHAR2 (10) DEPTNO NUMBER (3) SAL NUMBER (7,2) Allow NULL for all columns except ename and job. 2. Add constraints to check, while entering the empno value (i.e) empno > 100. 3. Define the field DEPTNO as unique. 4. Create a primary key constraint for the table(EMPNO). 5. Write queries to implement and practice constraints.

Referential Integrity Constraint: Foreign Key

Problem StatementWe have created employee and department tables with the below definition without adding foreign key relationTo maintain data integrity in the database, you are required to link the 'departmentId' from the 'department' table with the 'deptId' column in the 'employee' table. This is achieved by establishing a foreign key relationship between the two columns.Write an ALTER query for the 'employee' table to create a foreign key named 'deptIdFk,' referencing 'departmentId' from the 'department' table.Note:Write table name/ column name as given.Input format :The input tables are already prepopulated, as given in the problem statement.Output format :The output should display the detailed description of the employee table.Refer to the sample output for the column headers.Sample test cases :Input 1 :Output 1 :Field Type Null Key Default Extraid int NO PRI NULL name varchar(100) YES NULL address varchar(100) YES NULL age int YES NULL dob date YES NULL deptId int YES MUL NULL

Drop the NOT NULL constraints from EMP table

Write a query for the following.employee(eid,name, salary, address) department(d_id, d_name, eid)Give Primary Key, foreign key constraints after creating table with constraint names in given schemas.(1) Create a view department_details of department table.(2) Join two existing tables using inner join.(3) To drop a view