Many legacy systems require normalization Identify at least two factors that should be considered in order to ?produce an optimal normalized set of tables when performing ?normaliz

2 hours ago

sigma rahman

 

RE: Week 5 Discussion

Top of Form

 

Data normalization involves tabes and their relationships that evolve from the tables, these tables also have data that can be optimized at different levels of use and extraction, however, in order to design and protect the data/tables we have to remove any redundancy and of course inconsistent information/data, that I have noticed in several of my own work experiences. Where we have data in table formats that are often inconsistent, redundant and also missing. There are many factors that are required in order to have normalized data/tables, that is: identifiable sets of data, having different tables for different criteria, having primary and foreign keys, From all these in my opinion, the two most important factors are removing data redundancy and data inconsistency are the main factors that can affect the entire database. 

 

As per my two choices of factors, that includes data redundancy elimination, I found several online resources depicting the elimation of it, from personal experience also, below are some of the ways to do so:

1. Leveraging master data

2. Normalizing databases

3. Deleting unused data

4. Data management

 

Reference: Online resources:

1. What Is Data Redundancy & How Can You Avoid It?  https://datachannel.co/blogs/what-is-data-redundancy-how-can-you-avoid-it/

2. Data Redundancy: What Is It and How to Avoid It?  https://coresignal.com/blog/data-redundancy/

Bottom of Form

SAMPLE ANSWER

Identify at least two factors that should be considered in order to produce an optimal normalized set of tables when performing normalization.

Introduction

In this article, we will discuss the factors that should be considered when performing normalization. The first normal form should be followed, the second normal form should be followed and so on until there are no more tables left in your database.

The first normal form should be followed.

The first normal form should be followed.

The first normal form is a set of rules that dictate how a database should be structured in order to be considered normalized. This includes the rules about the structure of keys and their relationships, as well as the attributes themselves. In short, this means that each attribute should only depend on one key; if an attribute depends upon more than one key, then it’s not part of the first normal form (this can also mean that some attributes depend on no keys at all). This is also known as Boyce-Codd Normal Form or BCNF since they came up with these two names for different forms during their research into databases.

The second normal form should be followed.

The second normal form should be followed.

In order for an attribute to be a key, it must be functionally dependent on the whole key and not just part of it. A non-key attribute can only depend on one or more columns in a table’s primary key but not all of them. For example:

If you want to know if a user has been logged in since yesterday, you could use his username as your primary key (1st normal form). But if you wanted to know how many times he logged into Facebook this week (2nd normal form), then you would need additional information like his city and country code along with his username so that they could be used together in a query instead of just being placed inside another column or table row by themselves.*

The third normal form should be followed.

The third normal form should be followed for each table.

This means that the table must be in its own database and each column must have only one value for each row.

The third normal form is not required for all tables, but it is required when relationships are involved.

The fourth normal form should be followed.

The fourth normal form should be followed. A table is in the fourth normal form if it is in the third normal form and every non-prime attribute depends on every candidate key.

The fourth normal form is a special case of the fifth normal form, which requires that each non-prime attribute depends only on its own candidates for keys, but not any other attributes (other than its leftmost column).

The candidate keys for each table should be considered, and these keys should include at least one primary key and at least one candidate key.

The candidate keys for each table should be considered, and these keys should include at least one primary key and at least one candidate key. A candidate key is an index that can be used in several ways:

It can serve as a foreign key when joining tables.

It can also be used to identify rows within a single table (that is, it can serve as a unique constraint).

Candidate keys should be chosen carefully because they will affect performance of queries on both sides of the join operation.

Foreign key constraints should be considered.

Foreign key constraints should be considered. They are used to enforce referential integrity and ensure that the data in one table is consistent with the data in another table.

When using the fourth normal form, all composite keys should remain intact.

When using the fourth normal form, all composite keys should remain intact.

If a composite key is in use, it should be used in conjunction with the candidate key and primary key of a table.

Some or all of the above factors need to be considered in order to produce an optimal normalized set of tables when performing normalization

Some or all of the above factors need to be considered in order to produce an optimal normalized set of tables when performing normalization.

The first normal form should be followed, which means that each attribute in each table has only one NULL value and no duplicate values.

The second normal form should be followed, which means that each attribute in each table has at most one NOT NULL constraint and no other constraints (such as foreign key constraints).

The third normal form allows for attributes that are not unique but share a common type of value; this is also known as “multiple-valued key” tables or “cross joinable” data structures because they can be joined by their keys. The third normal form ensures that all attributes have unique values so there’s no chance for conflicting data between multiple records with the same unique key value; this prevents inconsistencies from occurring when comparing rows from different databases against each other due to differing column types between them (e.g., decimal vs string). However, if two columns don’t have any type restrictions set on them then they could still end up getting mixed up together during joins later down the road which would cause problems down stream too!

Conclusion

With this information, you can now begin to optimize your database design. You have learned that normalization is a necessary step in creating an effective database schema and that it should be considered from the very beginning of your project. You also know which factors need to be taken into account when performing normalization, so now it’s time to go out there and make those tables!