Skip to main content

SQL Set Operators

SQL Set Operators   Traditional Set Operators: Union Compatibility:     Requirement for the traditional set operators.    Strong requirement.                         - Same number of columns.                         - Each corresponding column is compatible.                         - Positional correspondence.     Apply to similar tables by removing columns first. SQL UNION Example:           Example 1: Retrieve basic data about all university people.                     SELECT FacNo AS PerNo, FacFirstName                                      ...

Identify the following Errors in Queries:

 a. Identify errors in the following SQL statement and label errors with error type. To simplify your work, the statement has only one type of error. Rewrite the statement to remove the error.

SELECT eventrequest.eventno, dateheld, status, estcost

FROM eventrequest, employee, facility, eventplan

WHERE estaudience > 5000

AND eventplan.empno = employee.empno

AND eventrequest.facno = facility.facno

AND facname = 'Football stadium'

AND empname = 'Mary Manager';

CORRECTION:

SELECT DISTINCT eventrequest.eventno, dateheld, status, estcost FROM eventrequest, employee, facility, eventplan

WHERE estaudience > 5000

AND eventplan.empno = employee.empno

AND eventrequest.facno = facility.facno

AND facname = 'Football stadium'

AND empname = 'Mary Manager';

ERROR

Missing join between event-plan and event-request tables. It results in incorrect number of rows.

ERROR TYPE:

Semantic Error.

b. Identify errors in the following SQL statement and label errors with error type. To simplify your work, the statement has only one type of error. Rewrite the statement to remove the error. 

SELECT DISTINCT eventrequest.eventno, dateheld, status, estcost

 FROM eventrequest, eventplan WHERE estaudience > 4000 

AND eventplan.eventno = eventrequest.eventno 

GROUP BY eventrequest.eventno, dateheld, status, estcost;


CORRECTION: 

SELECT DISTINCT eventrequest.eventno, dateheld, status, estcost 

FROM eventrequest, eventplan 

WHERE estaudience > 4000 

AND eventplan.eventno = eventrequest.eventno;


ERROR:

Group by classes are not needed.


ERROR TYPE:

Redundancy error.


c. Identify areas in which the SQL statement has poor coding practices and rewrite the statement to improve the coding practices. You do not need to search for errors.

SELECT eventplan.planno, lineno, resname, numberfld, timestart, timeend

FROM eventrequest, facility, eventplan, eventplanline, resourcetbl

WHERE estaudience = '10000'

AND eventplan.planno = eventplanline.planno

AND eventrequest.facno = facility.facno

AND facname = 'Basketball arena'

AND eventplanline.resno = resourcetbl.resno

AND eventrequest.eventno = eventplan.eventno 

Better Coding:

    SELECT eventplan.planno, lineno, resname, numberfld, timestart, timeend

    FROM eventrequest, facility, eventplan, eventplanline, resourcetbl

    WHERE estaudience = 10000

    AND eventplan.planno = eventplanline.planno

    AND eventrequest.facno = facility.facno

    AND eventplanline.resno = resourcetbl.resno

    AND eventrequest.eventno = eventplan.eventno







Our Official Website : Web Conquerors (https://www.webconquerors.com/) 

Want to get digital services? Contact US

Want to know about our services? Our Services

Comments

Popular posts from this blog

SQL Set Operators

SQL Set Operators   Traditional Set Operators: Union Compatibility:     Requirement for the traditional set operators.    Strong requirement.                         - Same number of columns.                         - Each corresponding column is compatible.                         - Positional correspondence.     Apply to similar tables by removing columns first. SQL UNION Example:           Example 1: Retrieve basic data about all university people.                     SELECT FacNo AS PerNo, FacFirstName                                      ...

Database Create Statements

University Database Create Statements :   DROP TABLE Enrollment; DROP TABLE offering; DROP TABLE Student; DROP TABLE Course; DROP TABLE Faculty;     -------------------- Student ------------------------   CREATE TABLE Student ( stdNo char(11) not null, stdFirstName varchar(30) not null, stdLastName varchar(30) not null, stdCity varchar(30) not null, stdState char(2) not null, stdZip char(10) not null, stdMajor char(6), stdClass char(2), stdGPA decimal(3,2), CONSTRAINT StudentPk PRIMARY KEY (StdNo) );     -------------------- Course ------------------------   CREATE TABLE Course ( CourseNo       char(6) not null, crsDesc        varchar(50) not null, CrsUnits       integer, CONSTRAINT CoursePK PRIMARY KEY (CourseNo) );     -------------------- Faculty ---------------------   CREAT...

Database Three Level Architecture

  Database Three Level Architecture Objectives of Three-Level Architecture: All users  should be able to access same data but have a different customized view.  A user’s view is immune to changes made in other views Users should not need to know physical database storage details.  DBA should be able to change database storage structures without affecting the user’s view.  Internal structure of database should be un affected by changes to physical aspects of storage. DBA should be able to change conceptual structure of database without affecting all users ANSI-SPARC Three-Level Architecture: External Level: Users’ view of the database .  Describes that part of database that is relevant to a particular user. Different views may have different representation of same data (e.g. different date formats, age derived from DOB etc.) Conceptual Level: Community view of the database. Describes what data is stored in the database and the relationships among the data....