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                                      ...

Correction For ERD

 d. For each consistency error in Figure 1, you should identify the consistency rule violated and suggest possible resolutions of the error. The ERD has generic names to help will concentrate on finding diagram errors rather than focusing on the meaning of the diagram.



Answer:


            Entity6 is violation of the Primary key rule. As there are 3 attributes from within Entity6 that are marked as primary key. Entity6 also violates the Identifying relationship rule, as there is no foreign key in the Entity6 table to identify the item from Entity7. Since this a weak entity type, the cardinality must be 1:1, which it is not. Entity2 is a violation of the Identifying relationship rule due to it not being a weak entity type when there is an identifying relationship.











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....