An ERD has m number of entities (strong, weak, parent, child all combined) andn number of relationship types (of all possible kinds). When transformed to the relational schema, Database designer come up with a solution which contained more than m+n relations. What could possibly be the reason? If you think the designer did a mistake then you can say that in your answer. Explain your answer if you think that will help. Answer:

An ERD has m number of entities (strong, weak, parent, child all combined) andn number of relationship types (of all possible kinds). When transformed to the relational schema, Database designer come up with a solution which contained more than m+n relations. What could possibly be the reason? If you think the designer did a mistake then you can say that in your answer. Explain your answer if you think that will help. Answer:

Principles of Information Systems (MindTap Course List)

12th Edition

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter5: Database Systems And Applications

Section5.7: Information Systems @ Work: Brandwatch: Applying Business Intelligence To Social Media Data To Make Advertising Decisions

Problem 1CTQ

See similar textbooks

Similar questions

Should the cardinality between entities be translated/read from both ends of the notation when dealing with database entity relationship modeling? To put it another way, can a connection between two things be comprehended by reading it both forward and backward?
Can you please help me in how I can turn the Entity Relationship diagram into a Logical Database Diagram? I know I need to list out all the entities, but I am not sure how to draw the relation. If you would please write it step by step for me so I can practice, that would be much appreciated.
Put into third Normal form where A,B, and C are prime attributes. Show the resulting 2NF and 3NF relations. Show work in relational notation R (A, B, C, D, E, F, G, H, I, J) FD1 B —> D, J FD2 (A, B, C) —> E FD3 F —> G, H FD4 C—> I FD5 A —> F
Design an Entity-Relationship for each system described below. Use the (min,max) notation. State clearly any additional assumptions you make. Give the relational model by applying the mapping rules (WITH REFERENCES AND ARROWS). NOTE: USE CHEN ER DIAGRAM (YOU CAN USE VISIO MICROSOFT(TEMPLATE=CHEN) ONLY SHOWING THE ENTITIES/ATTRIBUTES/WEAK ENTITIES/RELATIONSHIPS/PRIMARY KEY-FK/ (MIN-MAX) NOTATIONS ALSO NOT FORGETTING THE REFERENCES ON THE MAPPING TABLES WITH ARROWS REFERRING THE FOREIGN KEYS. YOUR WORK SHOULD BE SPECIFIC WITH JUSTIFICATION. We want to build a database for a community of paleontologists, storing information about the fossils kept in different museums. Each fossil is described by the year and place of discovery, the name of the paleontologist who discovered it, the room where it is exposed, and the presumed species. Each fossil may be assigned to different species with different degrees of probability. Museums are characterized by their rooms, their paleontologists and…
Consider the following relational schema for a library database: Book (Title, Author, Catalog_no, Publisher, Year, Price, bookCoverType, contractDate) Collection (Title, Author, Catalog_no) Assume {Author, Title} is the key for both relations Additional functional dependencies are Title,Author --> Catalog_no Catalog_no --> Publisher, Year, bookCoverType Publisher, bookCoverType --> Price Author --> contractDate a) Explain what normal form the relation is in. b) Apply normalization until the 3rd State reasons behind each normalization
Give a justification for why a relational database cannot support many-to-many relationships, and support your position with an example?
You are required to: Provide a normalized relational logical schema for the same database (NB It is not mandatory to report the restructured ER diagram) Define referential integrity constraints for 2 relationships of your choice among those defined in the conceptual schema solution: AUTHOR( author_id , name, surname) BOOK ( ISBN , title , num_page s , price ) CUSTOMER( customer_id , phone_number*, type, name*, surname*, vat_number*) CLERK( clerk_id , name) BUY( customer_id, clerk_id, ISBN ) WRITTEN_BY( author_id, ISBN ) 1) WRITTEN_BY (author_id) REFERENCES AUTHOR(author_id) WRITTEN_BY (ISBN) REFERENCES BOOK(ISBN) 2) BUY(customer_id) REFERENCES CUSTOMER(customer_id) BUY (clerk_id) REFERENCES CLERK(clerk_id) BUY (ISBN) REFERENCES BOOK (ISBN) i gave the solution. but i do not have any idea where it came from and how im supposed to formulate a similar solution so please help me understand how was this was reached and how i should solve these type of questions in…
Give a Relational Model that corresponds to the Entity-RelationshipDiagram in Figure 1. You must present this model as a RelationalDatabase Schema and not as a diagram. Primaryand foreign keys must be declared where required. Please keep thenames of attributes and role names where required and do not re-place them with different names. Provide NOT NULL constraintsonly where semantically justified by the Entity-Relationship diagram.
1. According to what you understand, what is the relationship between Functional Dependency and Normalization? 2. There are several attribute relationships, including partial dependency and transitive, give an example of the two relationships. 3. Why do we do the normalization stage in database design, especially in the logical stage?
Use MS Visio to create relational data schemas and data dependency diagrams for all entities (tables). Start out with listing all data attributes in 1NF, then label partial dependencies and potential transitive dependencies. For this Data. A database for payment and bookings for a Virginia Beach hotel. A guest can check into a hotel. A hotel can have many guests. A hotel can keep a record of a guest’s activities. A record can contain many notes. Possible tables might include: Guests, Notes, Room Type, Charges. Possible Primary keys might include: GuestID, NoteID, RoomID, ChargeCode. Possible attributes might include: CustName, Room#, ChargeType.
Read the following business rules carefully and use common sense when necessary to come up with a good database design as follows: 1- First, develop an ER model. Make sure to use meaningful entity names and relations. 2- Translate ER model into a set of tables, relations and constraints. 3- Label appropriate columns as primary keys and foreign keys. Business rules: A patient can make many appointments with one or more doctors in the clinic, and a doctor can accept appointments with many patients. However, each appointment is made with only one doctor and one patient. Emergency cases do not require an appointment. However, for appointment management purposes, an emergency is entered in the appointment book as “unscheduled.” If kept, an appointment yields a visit with the doctor specified in the appointment. The visit yields a diagnosis and, when appropriate, treatment. With each visit, the patient’s records are updated to provide a medical history Each patient visit…
What type of relationship in the conceptual model is converted to an entity in the logical database design?