BUS-120-Debriefing-paper-outline

.docx

School

San Jose State University *

*We aren’t endorsed by this school

Course

120B

Subject

Business

Date

May 17, 2024

Type

docx

Pages

Uploaded by SuperHumanThunder12272

Cao Kieu My Nguyen Trinh To Huynh Tran BUS 120 Debriefing paper outline 1. Please briefly describe some of the challenges encountered when building a database from an ER diagram with minimal user input. - Reading the ER diagram is hard to find the relationship with each entity. - When creating the tables in database, we have to decide which field should be the primary key. - When setting up the tables, we should be able to select the correct Data Type for each field. This step makes us the most confusing. o PostalCode: at first, we choose “Number”, and we want to limit with only 5 characters, we try to set “Field size” with 5, but with “Number” type there is drop box with default properties, such as Byte, Single, Long Integer, … We decide to choose “Short Text” type, then set field size with 5. o ProductNo appears in both “OrderDetails” and “Stocks” table. In “Stocks” table, it is primary key, so we think it should be “Auto Number” type. However, in “Orderdetails”, we set it “Number”. If we make relationship between these 2 tables, there will not have any connection, so we have to choose “Number” type. - Creating validity checks (Catalog in Stocks Table - Only H or S or F are valid. Quantity in Stocks Table - Have to be >= 0). It is a little confusing to put the statement into “Validation Rule” or “Validation Text”. We figure out that in Validation Rule it formats “Only H” Or “S” Or “F are valid”, which is in quotation mark is the one we have to fill out the table. It has to be “H” Or “S” Or “F”, and “Only H or S or F are valid” in Validation Text, which will pop up when we fill out other value except H, S, and F. 2. Please give a few recommendations about what information would be useful to have (that may not have been available for the project) when building a database. - Each table will have at least one entity which is included in another table to create a relationship. Therefore, we should consider carefully to select the correct Data Type. - PhoneNumber field, we can choose Data look with (***) ***-**** - Title and Rating field, we should create list box with value “Mr., Mrs, Ms.” and “1,2,3,4,5”  These could help us more convenient when filling out the tables. 3. The database in the exercise is a fully normalized database. In certain cases, database professionals may want to employ a non-normalized database. Give two examples of why you would want to normalize a database, and one example of why you would want to use a non-normalized database.

- The data is organized into the database which involves creating the tables and having relationships between them with the rules designed for protecting the data. Normalization is necessary whenever designing the database. This is dependent on the algorithm which would be used for the database. Having a normalized database would reduce the extra and invalid information optimizing the performance of the data. Normalization could be avoided in machine learning as each of the datasets does not require normalization. It also prevents any of the issues caused in the database during the modifications like deletion, insertion, and other things. When we try to run a query, normalization will give us an accurate data with matching our needs. - Some problems are accompanied by the normalization process. As the data is real and is not duplicated, joins for the table are required. Thus, queries become complicated and hence the read times become slow. With the lack of normalization, problems like performance issues and inaccurate data could be caused. Also, redundancy could put a load on the programs and would become difficult to modify.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version