Nt1330 Unit 2 Data Collection Paper

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

* As explained throughout this course, entity relationship modeling is a critical element of database design. If the database is not properly modeled, it is unlikely that the database will be properly developed. Using this knowledge, explain the key reasons why entity relationship modeling is important, and determine at least (1) way in which it impacts the overall development of the database.

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.

If we consider an example of a database for billing the claims to the provider, we have two tables in the database as ‘Claims’ and ‘Provider’. ‘Claims’ have the claim information such as (ClaimNumber, ClaimType, Type of service, Admission details) and ‘Provider’ have the provider information such as (ProviderID, FederalTaxID, NPI, PointOfService). The primary keys for ‘Claims’ is “ClaimNumber” and for ‘Provider’ is “ProviderID”.

The purpose of normalization is to create a stable set of relations is representative of the operations of an enterprise. By doing this we are able to reduce redundancy to save space and avoid inconsistencies in data. It also ensures that the design is free of certain updates, insertions, and deletion anomalies (Ricardo, 2012). With normalization as with most anything else there are advantages and disadvantages. The advantages of normalization are: ACID, which stands for atomicity, consistency, isolation, and durability. Atomicity means the transaction is a single unit. Either the entire set of actions is carried out or is not.

My thoughts on normalization is that it requires multi-steps to enter the data into tabular format to ensure they are well-organized in a way that is consistent and lacks redundancy as well as prevent unintended or unambiguous results. As stated by Demba (2013) that normalization in relational database design often involves the process of organizing data and dividing the database into two or more tables with defined relationships in order to minimize

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.

According to Kroenke and Auer (2010) there is an ERD standard, albeit very loosely practiced. The diagrams use combinations of rectangles and diamonds. Entity classes are shown using rectangles, relationships are shown using diamonds, the maximum cardinality of the relationship is shown inside the diamond, and the minimum cardinality is shown by the oval or hash mark next to the entity. The name of the entity is shown inside the rectangle and the name of the relationship is shown near the diamond.

It is a design method that used to avoid data redundancy and eliminate uncoordinated relationship. Normalisation has six stages to help with separate data which are UNF, 1NF, 2NF, 3NF, BCNF, 4NF and 5NF.

Foreign Key: When data is copied from one table to another for example when you copy a primary key to another table it will be duplicated to create a relationship. This is allowed and the table will then be called a foreign key.

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

A(n) FOREIGN KEY constraint is used to ensure that referential integrity exists between tables. _________________________

Data normalization is a process by which large tables are divided into smaller tables, and then relationships are defined between them. These relationships could be one-to-one, one-to-many, or many-to-many. The idea behind normalization is to eliminate redundant information and avoid data anomalies that could compromise the integrity of your data. Additionally, you can reduce the amount of space your database consumes and cut the need for

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 multivalued dependencies are:

Database design: An ORDBMS system usually adopts an entity-relationship (ER) or extended entity-relationship (E-ER) data model and an object-relational database design.