Integrity Rules Must Be Enforced By A Relational Dbms

713 Words2 Pages

A. Based on your understanding of the concept of integrity rules, Three (3) integrity rules must be enforced by a relational DBMS. List, and give a brief description of each of the three rules.

Answer: There are three integrity rules must be enforced by the relational Database Management System (DBMS) those are as follows:

I. Entity Integrity: primary key
• Each table must have a (Column’s) unique values
• No rows have a Missing values
• Ensure traceable entities here unique means not to have a same values

II. Referential Integrity: foreign keys
• Column value of one table must match column table of related table.
• Referential Integrity ensures database contain valid connections

III. Domain integrity: acceptable values for a column …show more content…

DBMS Complexity: During design phase optimum use the database must be very carefully designed. If not done well, the new system may fail to satisfy anyone. The complexity and breadth of the functions provided by a DBMS make it a complex product to use.
III. Greater Impact of failure: A failure is one of the vital reasons of any one user that damages the database and affects all the other users on the system. There are many cases we found all data is integrated into a single database. If database is corrupted due to various reasons like power failure or it is corrupted, then our valuable data may be lost or whole system stops.
IV. More difficult recovery: In general we regularly create data backup to protect the valuable data from damaging due to failures to the computer system or application program. If the data volume is large it’s really a time consuming. If the database is being updated by a large number of users, all update must be redone since the time of its restoration. Most of the DBMSs provide the 'backup and recovery ' sub-systems that automatically create the backup of data and restore data if system fails in the middle (or end) of an update operation of the …show more content…

What problem would you encounter if you wanted to produce a listing by city? How would you solve this problem by altering the file structure?
Answer:

Using this table (FIGURE P1.1) if I want to generate a list of city it is very difficult to generate at a time. Need huge initial work on address variable because it’s a composite address where city name is available but difficult to separate in a single query.

Having those in mind need to more carefully design the database structure where we can easily generate required outputs in any time, so create a separate city variable to solved the problem.

D. What data redundancies do you detect in the figure P1.1? How could those redundancies lead to anomalies?
Answer:

Manager_Phone and Manager_Address is data redundancies in the figure P1.1.

Unnecessary data being in the database is the definition of data redundancies. Don’t have one to one relationship data in a table. Here if Project Manager and Manager_Phone and Manager_Address one to one relation and no duplication so what’s harmed to redundancies and Manager_Phone and Manager_Address its unnecessary data and create database wide is bigger.

E. List and describe five data types that you will often encounter when working with

More about Integrity Rules Must Be Enforced By A Relational Dbms

Open Document