Mcb Week 1 Assignment

Which of the following defines a relationship in which each occurrence of data in one entity

The two parts in this assignment will contribute equally to your grade and will be evaluated separately.

A relational database is a database that consists of a collection of tables with columns showing entities, and rows showing data. This type of database uses a primary key and foreign key. The foreign key in another table will point to the primary key of a table, and this is how tables can relate to each other. This permits for one-to-one, one-to-many, and many-to-many relationship between the data. An advantage of relational databases includes the ease of adding or modifying new tables and entities without needing to change the structure of the database already in place. Relational database have many features, including indexing, setting data type, and setting validation tests, all these help to ensure data integrity.

1.4 For the tables you created in Review Question 1.3, what are the primary keys of each table? Do you think that any of these primary keys could be surrogate keys?

The challenging part was actually trying to understand what will be the best way to break a relation down into multiple relations without jeopardizing the integrity of the data at the same time. As I mention before it is not hard to do it but you really have to know how to do it.

There are three stages to normalization, 1st NF, 2nd NF, and 3rd NF. In the 1st NF stage must ensure that the table has no multivalued attributes. If there are the table should be broken down into separate tables so that there are no multivalued attributes. The 2nd NF stage requires that we break the tables down even more to ensure that all attributes and functional dependency entirely to the primary key and has met all requirements of the 1st NF. Then, and only then will it be considered to have met 2nd NF requirements. To transform the database to 3rd NF you must identify the primary key in the 2nd NF table. Then we must identify functional dependencies in the relationship to ensure there are no transitive dependencies. These types of dependencies can cause insertion, deletion, and update

Hence, this session has enhanced my understanding about normalization and how essential to create a data that is well organized with the relationships clearly defined and established between the tables (based on the business rules) in order to eliminate data redundancy and inconsistency.

Save a copy of your assignments: You may need to re-submit an assignment at your instructor’s request. Make sure you save your files in accessible location.

2NF (Second Normal Form): The relation should not have any partial dependencies; part of the primary key should not identify a subset of attributes in the same table. The relation must be in 1NF before it can be in 2NF [12]

Use relationships to manage dependencies. Many assets have dependencies, or requirements that are beyond the asset itself in order to be complete, to work, or to build. For example a Build or an Implementation asset type might have dependencies that are required for the asset to be complete or valid. Assets may require certain binary and jar files that are dependencies for the build or implementation.

When it comes to the data model, there exists a relationship that has three different representations for the reason that database requires the relationship between the tables. It goes hand-in-hand with one another without the relationship the tables would have no purpose. The information cannot be repetitive in order for the each table to work and provide the specific database that is related to the information. In different ways the tables in the Huffman Trucking Fleet Truck database

the instances of a subtype do not participate in a relationship that is unique to that subtype.

| (TCO A) Projects have specific attributes. Which of the following is not an attribute?

We will assume that Number  Name where name is not unique (i.e., there may be more than one “John Smith”, each with a different student number). Then the functional dependencies are:

4) Designate relationships and attributes from the source data. Relationships are derived from ingredients, pill imprint information