Unit 18 Database Design Oliver Taylor Resubmission

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

In social databases, a one-to-numerous relationship happens when a parent record in one table can possibly reference a few youngster records in another table. In a one-to-numerous relationship, the parent is not required to have youngster records; in this way, the one-to-numerous relationship permits zero tyke records, a solitary kid record or various kid records. The imperative thing is that the youngster can't have more than one parent record.

Be sure to provide a detailed explanation of relational databases along with their associated business advantages.

Relational Database Management Systems are probably the ones that we are most familiar with in 21st century computer science. Relational databases store

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.

To answer each question, darken the circle corresponding to your answer using a pencil. If you decide to change your answer, please erase your original answer completely and darken your new answer.

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

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

Business Rules: In the entity-relationship data models, business rules must take into account all relationship models: one-to-many (1:M), one-to-one (1:1) and many-to-many (M:N). For a database on a school library, a restriction of having a student only allowed to borrow one book would need a 1:1 relationship.

One of the main components of a database is characters. Characters are letters, numbers and punctuation marks. You are using characters when you are typing a sentence for example. Another main component would be fields. Fields separate data in defined fields. When data is being entered even if you don’t have an answer for all fields a space is still left but it would be blank. If you have ever seen an excel spreadsheet that would give you an idea of how data is lined out into different fields. Records are a main database component as well. Records are a group of fields that are about one thing. An example would be social security numbers in a database of patients. Each patient would have a social security number and each social security number is in a field. That field would have the same information which is that patients social security number even though every ones is different and there would be many listed depending on how many patients was in the database. Gartee, R. (2011).

By applying this rule, patient and employees table has to be divided into smaller tables. Patient table limits hospital to enter more than one appointment, drug allergy, symptom, prescription entries.

Example 1 – Consider the following relational database for the Super Baseball League. It keeps track of teams in the league, coaches and players on the teams, work experience of the coaches, bats belonging to each team, and which players have played on which teams. Note the following facts about this environment:

Firstly a relational database contains a set of tables which basically are linked collectively by the relationships between the tables. Also it is also known as reason such as a database is called relational database.

In a RDBMS, the tables will have an identifier called primary key. Data values will be stored in the form of tables. The relationships between these data values will be stored in the form of a table as well. Every value stored in the relational database is accessible. This value can be updated by the system. The data in this system is also physically and logically