There are three to answer in 83 WORDS each! And just from the tutor view point no need to use the APA thanks a lot
1)
I hope everyone is having a great week so far. Unit 2 was very interesting as we were learning and teaching each other on how databases are built and what clauses and SQL statements are used when building a database.
In our unit 3 we are focusing on Pitt Fitness exercise in our chapter 5 readings. The idea is to assume the field LengthOfTime has data such as 60 minutes, 30 minutes, 1 hour, and 15 minutes. The question is asking us if this is the correct way to record the data. In my opinion it is not the correct way to record the data. When we look at the field values of the attributes, we see that it contains values of different data units, such as hours and minutes, which makes the data inaccurate.
The best solution to this would be to insert data into the table using minutes. Because if you really think about it, data in hours can be converted to minutes and represented as the''integer"data type. Previously, we've learned that "integer" (int) is a whole number that can be positive, negative, or a zero.
The database for Pitt Fitness needs to be normalized. To normalize Pitt Fitness data, I would need to progress through normal forms: first normal form (1NF) second normal form (2NF), third normal form (3NF) and finally the fourth normal form (4NF).
When normalizing data, we need to first look at the repeated fields for Pitt Fitness and sort those repeated fields in separate files and assign appropriate keys to those files. The relationship in a table is in first normal form (1NF). In our readings, it states the following: removing repeating groups is the starting point to move an unnormalized relation to the tabular data format of 1NF, the starting point of a relational database (Friedrichsen, Ruffolo, & Monk, 2020).
In the second normal form (2NF), I would organize the columns into smaller relations. In this stage, a table relation is considered in second
2)
First Normal Form - The first step is to ensure each column contains one value, consistent, are atomic values, and with no duplicate records. An atomic value is a piece of information that cannot be divided (Friedrichsen et al., 2020, p. 172).
Second Normal Form- First it must meet all the requirements in the previous step. The second step is to organize the columns into smaller tables. Second normal form requires each non-key attributes is fully dependent on the primary key.
Third Normal Form - Again must meet the requirements in the previous step. The third step is to ensure there are no transitive dependencies. This normal form is also known as the Boyce-Codd Normal Form (Friedrichsen et al., 2020, p. 190).
Fourth Normal Form- Again must meet the requirements in the previous step. The fourth step is to ensure there are no multi-valued dependency. GeeksforGeeks define Multi-Valued Dependency as " when there are two attributes in a table which depend on a third attribute but are independent of each other" (2020, para. 1).
References
Difference between 4NF and 5NF. GeeksforGeeks. (2020, May 20). Retrieved January 21, 2022, from https://www.geeksforgeeks.org/difference-between-4nf-and-5nf/
Friedrichsen, L., Ruffolo, L., Monk, E. (20200304). Concepts of Database Management, 10th Edition. [VitalSource Bookshelf 10.0.1]. Retrieved from vbk://9780357885697
3)
he first thing that came to mind was the fact that it said 60 minutes then 1 hour, but then it was realized that it was an hour and 15 minutes. I feel like that could confuse people if not seen correctly. To make a table with this data, it would be better to put a Length of Time spot as one column. This is said because there is no need for 3 extra columns just to checkmark what class is taken. It would be easier to just write down the time allotted.
Instead of doing Class (LengthofTime, 60min, 30min, 1hourand15min), It should just be Class (LengthofTime). This way it can just be inputted when the time comes. It is more simplistic and just overall to understand. Another possibility could be making 3 different tables and putting the information of each length class. For example, have a table for 60 min, 30 min, and a table for 1 hour and 15 min. Then put the personal information, the Customer ID, the Class ID, and the instructor.
Class (
LastName
FirstName
CustomerID
ClassID
Instructor);
According to our textbook, “the normalization process is a series of progressive steps you follow to identify and correct data redundancy and integrity problems that occur when data is stored in one large table,” (Friedrichsen, L., Ruffolo, L., & Monk, E., 2020). This basically helps create smaller tables so there is no confusion or redundancy in the data. As stated earlier, if 3 different tables were made for the length of time, then the data would show more consistency and reliability. Sometimes it is better to make a few tables, than one big one so it does not cause trouble when putting data in and more people go to these classes. There is also the tables that could be separated due to the type of class.
Class 1 (
LastName
FirstName
CustomerID
InstructorID
LengthofTime );
This could be the outline for all normalized data to keep track of everything much easier instead of one big table. There could be a folder for each class or length of time depending on what table is created. There are many ways that this can be done, so it really depends on what is easier for people when they create it.
Friedrichsen, L., Ruffolo, L., & Monk, E. (2020). Concepts of Database Management (10th Edition). Cengage Limited. https://aiu.vitalsource.com/books/9780357885697