Untuk menghindari kejahatan di dunia maya, selalu ditekankan prinsip dasar yang harus diketahui dalam menggunakan internet. Prinsip dasar di dunia nyata berlaku pula di dunia maya. Penggunaan internet secara sehat dan aman perlu ditanamkan semenjak dini melalui pembelajaran etika berinternet secara sehat (cyber ethics). Hal ini perlu disampaikan untuk menghindari kebiasaan jelek di dunia nyata akan terbawa di dunia maya dan menimbulkan kembali efek negatif di dunia nyata.
Chapter 7
Logical Database Design
BLCN-534: Fundamentals of Database Systems
Chapter ObjectivesDescribe the concept of logical database design. Design relational databases by converting entity-relationship diagrams into relational tables. Describe the data normalization process.Perform the data normalization process. Test tables for irregularities using the data normalization process.
7-*
Logical Database DesignThe process of deciding how to arrange the attributes of the entities in the business environment into database structures, such as the tables of a relational database.The goal is to create well structured tables that properly reflect the company’s business environment.
7-*
Logical Design of Relational Database Systems(1) The conversion of E-R diagrams into relational tables.(2) The data normalization technique.(3) The use of the data normalization technique to test the tables resulting from the E-R diagram conversions.
7-*
Converting E-R Diagrams into Relational TablesEach entity will convert to a table.Each many-to-many relationship or associative entity will convert to a table.During the conversion, certain rules must be followed to ensure that foreign keys appear in their proper places in the tables.
7-*
Converting a Simple EntityThe table simply contains the attributes that were specified in the entity box.Salesperson Number is underlined to indicate that it is the unique identifier of the entity and the primary key of the table.
7-*
Converting Entities in Binary Relationships: One-to-OneThere are three options for designing tables to represent this data.
7-*
One-to-One: Option #1The two entities are combined into one relational table.
7-*
One-to-One: Option #2
Separate tables for the SALESPERSON and OFFICE entities, with Office Number as a foreign key in the SALESPERSON table.
7-*
One-to-One: Option #3Separate tables for the SALESPERSON and OFFICE entities, with Salesperson Number as a foreign key in the OFFICE table.
7-*
Converting Entities in Binary Relationships: One-to-ManyThe unique identifier of the entity on the “one side” of the one-to-many relationship is placed as a foreign key in the table representing the entity on the “many side.”So, the Salesperson Number attribute is placed in the CUSTOMER table as a foreign key.
7-*
Converting Entities in Binary Relationships: One-to-Many
7-*
Converting Entities in Binary Relationships: Many-to-ManyE-R diagram with the many-to-many binary relationship and the equivalent diagram using an associative entity.
7-*
Converting Entities in Binary Relationships: Many-to-ManyAn E-R diagram with two entities in a many-to-many relationship converts to three relational tables.Each of the two entities converts to a table with its own attributes but with no foreign keys (regarding this relationship).In addition, there must be a third “many-to-many” table for the many-to-many relationship.
7-*
Converting Entities in Binary Relationships: Many-to-Man ...
Business users like you often have to create summary reports out of the data you have. Writing formulae, providing information and organizing the totals into a new table take up valuable time!
E.g., Imagine you have created the perfect summary report that compares, say, sales in different rE.g. ions. You may also have to compare sales across different product lines or customers.
To ease your efforts, Excel supports a feature called ‘pivot table’ which helps in summarizing your data. Moreover, you can easily generate multiple summary reports from the same pivot table.
The best part is, Collabion Charts for SharePoint supports basic pivoting features. It lets you create insightful charts based on pivot tables.
How?
Take a peek at the slides below to get to know!
Chapter 7
Logical Database Design
BLCN-534: Fundamentals of Database Systems
Chapter ObjectivesDescribe the concept of logical database design. Design relational databases by converting entity-relationship diagrams into relational tables. Describe the data normalization process.Perform the data normalization process. Test tables for irregularities using the data normalization process.
7-*
Logical Database DesignThe process of deciding how to arrange the attributes of the entities in the business environment into database structures, such as the tables of a relational database.The goal is to create well structured tables that properly reflect the company’s business environment.
7-*
Logical Design of Relational Database Systems(1) The conversion of E-R diagrams into relational tables.(2) The data normalization technique.(3) The use of the data normalization technique to test the tables resulting from the E-R diagram conversions.
7-*
Converting E-R Diagrams into Relational TablesEach entity will convert to a table.Each many-to-many relationship or associative entity will convert to a table.During the conversion, certain rules must be followed to ensure that foreign keys appear in their proper places in the tables.
7-*
Converting a Simple EntityThe table simply contains the attributes that were specified in the entity box.Salesperson Number is underlined to indicate that it is the unique identifier of the entity and the primary key of the table.
7-*
Converting Entities in Binary Relationships: One-to-OneThere are three options for designing tables to represent this data.
7-*
One-to-One: Option #1The two entities are combined into one relational table.
7-*
One-to-One: Option #2
Separate tables for the SALESPERSON and OFFICE entities, with Office Number as a foreign key in the SALESPERSON table.
7-*
One-to-One: Option #3Separate tables for the SALESPERSON and OFFICE entities, with Salesperson Number as a foreign key in the OFFICE table.
7-*
Converting Entities in Binary Relationships: One-to-ManyThe unique identifier of the entity on the “one side” of the one-to-many relationship is placed as a foreign key in the table representing the entity on the “many side.”So, the Salesperson Number attribute is placed in the CUSTOMER table as a foreign key.
7-*
Converting Entities in Binary Relationships: One-to-Many
7-*
Converting Entities in Binary Relationships: Many-to-ManyE-R diagram with the many-to-many binary relationship and the equivalent diagram using an associative entity.
7-*
Converting Entities in Binary Relationships: Many-to-ManyAn E-R diagram with two entities in a many-to-many relationship converts to three relational tables.Each of the two entities converts to a table with its own attributes but with no foreign keys (regarding this relationship).In addition, there must be a third “many-to-many” table for the many-to-many relationship.
7-*
Converting Entities in Binary Relationships: Many-to-Man ...
Business users like you often have to create summary reports out of the data you have. Writing formulae, providing information and organizing the totals into a new table take up valuable time!
E.g., Imagine you have created the perfect summary report that compares, say, sales in different rE.g. ions. You may also have to compare sales across different product lines or customers.
To ease your efforts, Excel supports a feature called ‘pivot table’ which helps in summarizing your data. Moreover, you can easily generate multiple summary reports from the same pivot table.
The best part is, Collabion Charts for SharePoint supports basic pivoting features. It lets you create insightful charts based on pivot tables.
How?
Take a peek at the slides below to get to know!
Part 2Supplier Database (MS Access)As you recall, data is a.docxodiliagilby
Part 2:
Supplier Database (MS Access)
As you recall, data is a collection of facts (numbers, text, even audio and video files) that is processed into usable information. Much like a spreadsheet, a database is a collection of such facts that you can then slice and dice in various ways to extract information or make decisions. However, the advantage and primary use of a database over a spreadsheet is its ability to handle a large volume of data and yet allow for quick access to the information that is desired.
Databases are everywhere now and impact our lives in a multitude of ways. It can accurately be said that “your life is in a database” or, more accurately, in multiple databases, and information about you (a retrieval of facts about you) is easily accessible. Your shopping history, credit history, medical history, even your driving history, is stored in one or more databases.
This exercise will introduce you to the basic building blocks of any database – fields, records, and files (also called tables). Although you will create a database with a single table containing a small amount of data about computer component suppliers, the more applicable use of databases involves the creation of many tables linked together with a common field or “key.” Regardless of the size of the database, the data is stored in the same way – in fields which are combined to create a record. And those records are stored in a file or table. The data is entered into the field via a data entry form, and the information is extracted (to answer a particular question or need) via reports and/or queries.
Specific instructions for the project can be found in the table below.
Create a supplier database and related reports and queries to capture contact information for potential PC component suppliers that might be used to purchase the equipment your specified in your MS Word project – the PC specifications..
This MS Access database assignment has the following parts:
a simple database
table
to hold supplier contact information; some of the required fields in the table require that a Caption be added to the field characteristics. The Caption will be displayed in the report that is to be generated.
a simple database
form
that can be used to enter data into the database table;
two
simple database
reports
that can used to present the data as information; and
a separate MS Word
document
answering questions about the database.
All aspects of the assignment will be evaluated according to the following criteria and overall professional, business-like appearance. This would include clear readability and formatting for both screen and print-based output.
Element #
Requirement
Points Allocated
Comments
01
·
Launch MS Access and open a Blank Access database.
·
Save the new database
with the following name:
“
Student’s First Initial Last Name Supplier Information
”
Example:
JSmith Supplier Information
0.1
Create a table with all the following fiel.
Find Top SQL Developers today. Toptal can match you with the best engineers to finish your project. Or, match you with the best companies that need your SQL skills today!
Lamar University - MISY 3310 Access ProjectPremiere Products.docxDIPESH30
Lamar University - MISY 3310
Access Project
Premiere Products – Data Management
Premiere Products is a distributor of appliances, house wares, and sporting goods. Since its inception, the company has used spreadsheet software to maintain customer, order, inventory, and sales representative data. Redundancy and difficulty in accessing related data are the major problems that employees at Premiere Products encounter with the spreadsheets. The company’s business activities have grown significantly in the recent years and it is no longer feasible to use spreadsheets to maintain its data.
The management of Premiere Products has determined that Premiere Products must maintain, in a new database, the following information about its sales representatives, customers, parts inventory, and suppliers:
· Premiere Products must store the sales rep number that uniquely identifies a representative. In addition, it has to store the sales rep last name, first name, address, total commission, and commission rate.
· The company must store the customer number, which uniquely identifies a customer, customer name, address, current balance, and credit limit for each customer, as well as the number of sales representative who represents the customer.
· The company must store the part number, description, number of units on hand, item type, number of the warehouse where the item is stored, and unit price for each part in inventory.
· Premiere Products must store information about the suppliers who supply parts. The supplier is uniquely identified by supplier number. In addition, a supplier has a name, address, city, contact name and telephone number.
Premiere Products must also store information about orders. The orders have three components: The heading (top) of the order contains the order number and the date; the customer’s number, name, and address; and the sales rep number and name. The body of the order contains one or more order lines, sometimes called line items. Each order line contains a part number, a part description, the number of units of the part ordered, and the quoted price for the part. Each order line also contains a total, usually called an extension, which is the result of multiplying the number ordered by the quoted price. Finally, the footing (bottom) of the order contains the order total.
Premiere Products must also store the following items for each customer’s order:
· For each order, they must store the order number, the date the order was placed, and the number of the customer that placed the order. The customer’s name and address and the number of the sales rep who represents the customer are stored with the customer information. The name of the sales rep is stored with the sales rep information.
· For each order line, the database must store the order number, the part number, the number of units ordered, and the quoted price. Remember that the part description is stored with the information about parts. The result of mu ...
Part 2Provider Database (MS Access)For a review of the complete r.docxherbertwilson5999
Part 2:Provider Database (MS Access)For a review of the complete rubric used in grading this exercise, click on the Assignments tab, then on the title Case Study Part 2 - Provider Database (Access)– click on Show Rubrics if the rubric is not already displayed.
As you recall, data is a collection of facts (numbers, text, even audio and video files) that is processed into usable information. Much like a spreadsheet, a database is a collection of such facts that you can then slice and dice in various ways to extract information or make decisions. However, the advantage and primary use of a database over a spreadsheet is its ability to handle a large volume of data and yet allow for quick access to the information that is desired.
Databases are everywhere now and impact our lives in a multitude of ways. It can accurately be said that “your life is in a database” or, more accurately, in multiple databases, and information about you (a retrieval of facts about you) is easily accessible. Your shopping history, credit history, medical history, even your driving history, is stored in one or more databases.
This exercise will introduce you to the basic building blocks of any database – fields, records, and files (also called tables). Although you will create a database with a single table containing a small amount of data about computer component Providers, the more applicable use of databases involves the creation of many tables linked together with a common field or “key.” Regardless of the size of the database, the data is stored in the same way – in fields which are combined to create a record. And those records are stored in a file or table. The data is entered into the field via a data entry form, and the information is extracted (to answer a particular question or need) via reports and/or queries. Specific instructions for the project can be found in the table below.
Create a provider database and related reports and queries to capture contact information for potential PC component providers that might be used to purchase the equipment your specified in your MS Word project – the PC specifications..
This MS Access database assignment has the following parts:
1. a simple database table to hold provider contact information; some of the required fields in the table require that a Caption be added to the field characteristics. The Caption will be displayed in the report that is to be generated.
1. a simple database form that can be used to enter data into the database table;
1. two simple database reports that can used to present the data as information; and
1. a separate MS Word document answering questions about the database.
All aspects of the assignment will be evaluated according to the following criteria and overall professional, business-like appearance. This would include clear readability and formatting for both screen and print-based output.
Element #
Requirement
Points Allocated
Comments
01
· Launch MS Access and open .
Essbase’s “Best in Class” calculation engine enables Essbase and Planning to satisfy a vast array of planning and analysis needs. Whether it’s on-premise, in PBCS custom databases, or in the EPBCS business processes, creating custom logic that meets any analytical need will generate enormous value for your organization. But to take advantage of that power and avoid costly mistakes, you must thoroughly understand what you’re working with.
The Visual Approach to Essbase calculations was developed and refined over 20 years of Essbase and Planning projects with thousands of hours of training. Now, it’s been updated for the cloud and Hybrid Aggregation. The Visual Approach uses many diagrams and visualizations to walk through exactly how Essbase thinks, starting with a thorough explanation of dimensionality, the Essbase calc cycle, global calculation, and controlling calculation scope. It demystifies sparse and dense, showing how to make the block your friend in order to make your calculations (and other Essbase/Planning operations) quickly. Finally, it explains a handful of the most important commands and functions.
This presentation is for power users, admins, and developers who are either new to Essbase and Planning calculations or need to improve their calculation skills. It provides a thorough understanding of the concepts governing Essbase calculations and the core set of commands and functions that are used in virtually every calc script and business rule. It gives you the confidence to tackle new calculation challenges and write better, faster, and more powerful business rules.
Part 2Provider Database (Open Office Database)Use the project.docxdewhirstichabod
Part 2:
Provider Database (Open Office Database)
Use the project description HERE to complete this activity. For a review of the complete rubric used in grading this exercise, click on the Assignments tab, then on the title
Case Study Part 2 - Provider Database (Access)
– click on Show Rubrics if the rubric is not already displayed. The grading rubric has been built for use with MS Access. However, the elements graded and the point value for each element is identical for anyone using OO for this assignment.
NOTE: there are some great tutorials on working with OpenOffice which can be found in the Content menu. Look for the
Tutorials
menu item in the section under
OpenOffice - Database Alternative for Mac OS X
.
As you recall, data is a collection of facts (numbers, text, even audio and video files) that is processed into usable information. Much like a spreadsheet, a database is a collection of such facts that you can then slice and dice in various ways to extract information or make decisions. However, the advantage and primary use of a database over a spreadsheet is its ability to handle a large volume of data and yet allow for quick access to the information that is desired.
Databases are everywhere now and impact our lives in a multitude of ways. It can accurately be said that “your life is in a database” or, more accurately, in multiple databases, and information about you (a retrieval of facts about you) is easily accessible. Your shopping history, credit history, medical history, even your driving history, is stored in one or more databases.
This exercise will introduce you to the basic building blocks of any database – fields, records, and files (also called tables). Although you will create a database with a single table containing a small amount of data about computer component Providers, the more applicable use of databases involves the creation of many tables linked together with a common field or “key.” Regardless of the size of the database, the data is stored in the same way – in fields which are combined to create a record. And those records are stored in a file or table. The data is entered into the field via a data entry form, and the information is extracted (to answer a particular question or need) via reports and/or queries.
Specific instructions for the project can be found in the table below.
Create a provider database and related reports and queries to capture contact information for potential PC component providers that might be used to purchase the equipment your specified in your MS Word project – the PC specifications..
This Open Office database assignment has the following parts:
a simple database
table
to hold provider contact information; some of the required fields in the table require that a Caption be added to the field characteristics. The Caption will be displayed in the report that is to be generated.
a simple database
form
that can be used to enter data into the database table;
a simp.
Honest Reviews of Tim Han LMA Course Program.pptxtimhan337
Personal development courses are widely available today, with each one promising life-changing outcomes. Tim Han’s Life Mastery Achievers (LMA) Course has drawn a lot of interest. In addition to offering my frank assessment of Success Insider’s LMA Course, this piece examines the course’s effects via a variety of Tim Han LMA course reviews and Success Insider comments.
More Related Content
Similar to 2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx
Part 2Supplier Database (MS Access)As you recall, data is a.docxodiliagilby
Part 2:
Supplier Database (MS Access)
As you recall, data is a collection of facts (numbers, text, even audio and video files) that is processed into usable information. Much like a spreadsheet, a database is a collection of such facts that you can then slice and dice in various ways to extract information or make decisions. However, the advantage and primary use of a database over a spreadsheet is its ability to handle a large volume of data and yet allow for quick access to the information that is desired.
Databases are everywhere now and impact our lives in a multitude of ways. It can accurately be said that “your life is in a database” or, more accurately, in multiple databases, and information about you (a retrieval of facts about you) is easily accessible. Your shopping history, credit history, medical history, even your driving history, is stored in one or more databases.
This exercise will introduce you to the basic building blocks of any database – fields, records, and files (also called tables). Although you will create a database with a single table containing a small amount of data about computer component suppliers, the more applicable use of databases involves the creation of many tables linked together with a common field or “key.” Regardless of the size of the database, the data is stored in the same way – in fields which are combined to create a record. And those records are stored in a file or table. The data is entered into the field via a data entry form, and the information is extracted (to answer a particular question or need) via reports and/or queries.
Specific instructions for the project can be found in the table below.
Create a supplier database and related reports and queries to capture contact information for potential PC component suppliers that might be used to purchase the equipment your specified in your MS Word project – the PC specifications..
This MS Access database assignment has the following parts:
a simple database
table
to hold supplier contact information; some of the required fields in the table require that a Caption be added to the field characteristics. The Caption will be displayed in the report that is to be generated.
a simple database
form
that can be used to enter data into the database table;
two
simple database
reports
that can used to present the data as information; and
a separate MS Word
document
answering questions about the database.
All aspects of the assignment will be evaluated according to the following criteria and overall professional, business-like appearance. This would include clear readability and formatting for both screen and print-based output.
Element #
Requirement
Points Allocated
Comments
01
·
Launch MS Access and open a Blank Access database.
·
Save the new database
with the following name:
“
Student’s First Initial Last Name Supplier Information
”
Example:
JSmith Supplier Information
0.1
Create a table with all the following fiel.
Find Top SQL Developers today. Toptal can match you with the best engineers to finish your project. Or, match you with the best companies that need your SQL skills today!
Lamar University - MISY 3310 Access ProjectPremiere Products.docxDIPESH30
Lamar University - MISY 3310
Access Project
Premiere Products – Data Management
Premiere Products is a distributor of appliances, house wares, and sporting goods. Since its inception, the company has used spreadsheet software to maintain customer, order, inventory, and sales representative data. Redundancy and difficulty in accessing related data are the major problems that employees at Premiere Products encounter with the spreadsheets. The company’s business activities have grown significantly in the recent years and it is no longer feasible to use spreadsheets to maintain its data.
The management of Premiere Products has determined that Premiere Products must maintain, in a new database, the following information about its sales representatives, customers, parts inventory, and suppliers:
· Premiere Products must store the sales rep number that uniquely identifies a representative. In addition, it has to store the sales rep last name, first name, address, total commission, and commission rate.
· The company must store the customer number, which uniquely identifies a customer, customer name, address, current balance, and credit limit for each customer, as well as the number of sales representative who represents the customer.
· The company must store the part number, description, number of units on hand, item type, number of the warehouse where the item is stored, and unit price for each part in inventory.
· Premiere Products must store information about the suppliers who supply parts. The supplier is uniquely identified by supplier number. In addition, a supplier has a name, address, city, contact name and telephone number.
Premiere Products must also store information about orders. The orders have three components: The heading (top) of the order contains the order number and the date; the customer’s number, name, and address; and the sales rep number and name. The body of the order contains one or more order lines, sometimes called line items. Each order line contains a part number, a part description, the number of units of the part ordered, and the quoted price for the part. Each order line also contains a total, usually called an extension, which is the result of multiplying the number ordered by the quoted price. Finally, the footing (bottom) of the order contains the order total.
Premiere Products must also store the following items for each customer’s order:
· For each order, they must store the order number, the date the order was placed, and the number of the customer that placed the order. The customer’s name and address and the number of the sales rep who represents the customer are stored with the customer information. The name of the sales rep is stored with the sales rep information.
· For each order line, the database must store the order number, the part number, the number of units ordered, and the quoted price. Remember that the part description is stored with the information about parts. The result of mu ...
Part 2Provider Database (MS Access)For a review of the complete r.docxherbertwilson5999
Part 2:Provider Database (MS Access)For a review of the complete rubric used in grading this exercise, click on the Assignments tab, then on the title Case Study Part 2 - Provider Database (Access)– click on Show Rubrics if the rubric is not already displayed.
As you recall, data is a collection of facts (numbers, text, even audio and video files) that is processed into usable information. Much like a spreadsheet, a database is a collection of such facts that you can then slice and dice in various ways to extract information or make decisions. However, the advantage and primary use of a database over a spreadsheet is its ability to handle a large volume of data and yet allow for quick access to the information that is desired.
Databases are everywhere now and impact our lives in a multitude of ways. It can accurately be said that “your life is in a database” or, more accurately, in multiple databases, and information about you (a retrieval of facts about you) is easily accessible. Your shopping history, credit history, medical history, even your driving history, is stored in one or more databases.
This exercise will introduce you to the basic building blocks of any database – fields, records, and files (also called tables). Although you will create a database with a single table containing a small amount of data about computer component Providers, the more applicable use of databases involves the creation of many tables linked together with a common field or “key.” Regardless of the size of the database, the data is stored in the same way – in fields which are combined to create a record. And those records are stored in a file or table. The data is entered into the field via a data entry form, and the information is extracted (to answer a particular question or need) via reports and/or queries. Specific instructions for the project can be found in the table below.
Create a provider database and related reports and queries to capture contact information for potential PC component providers that might be used to purchase the equipment your specified in your MS Word project – the PC specifications..
This MS Access database assignment has the following parts:
1. a simple database table to hold provider contact information; some of the required fields in the table require that a Caption be added to the field characteristics. The Caption will be displayed in the report that is to be generated.
1. a simple database form that can be used to enter data into the database table;
1. two simple database reports that can used to present the data as information; and
1. a separate MS Word document answering questions about the database.
All aspects of the assignment will be evaluated according to the following criteria and overall professional, business-like appearance. This would include clear readability and formatting for both screen and print-based output.
Element #
Requirement
Points Allocated
Comments
01
· Launch MS Access and open .
Essbase’s “Best in Class” calculation engine enables Essbase and Planning to satisfy a vast array of planning and analysis needs. Whether it’s on-premise, in PBCS custom databases, or in the EPBCS business processes, creating custom logic that meets any analytical need will generate enormous value for your organization. But to take advantage of that power and avoid costly mistakes, you must thoroughly understand what you’re working with.
The Visual Approach to Essbase calculations was developed and refined over 20 years of Essbase and Planning projects with thousands of hours of training. Now, it’s been updated for the cloud and Hybrid Aggregation. The Visual Approach uses many diagrams and visualizations to walk through exactly how Essbase thinks, starting with a thorough explanation of dimensionality, the Essbase calc cycle, global calculation, and controlling calculation scope. It demystifies sparse and dense, showing how to make the block your friend in order to make your calculations (and other Essbase/Planning operations) quickly. Finally, it explains a handful of the most important commands and functions.
This presentation is for power users, admins, and developers who are either new to Essbase and Planning calculations or need to improve their calculation skills. It provides a thorough understanding of the concepts governing Essbase calculations and the core set of commands and functions that are used in virtually every calc script and business rule. It gives you the confidence to tackle new calculation challenges and write better, faster, and more powerful business rules.
Part 2Provider Database (Open Office Database)Use the project.docxdewhirstichabod
Part 2:
Provider Database (Open Office Database)
Use the project description HERE to complete this activity. For a review of the complete rubric used in grading this exercise, click on the Assignments tab, then on the title
Case Study Part 2 - Provider Database (Access)
– click on Show Rubrics if the rubric is not already displayed. The grading rubric has been built for use with MS Access. However, the elements graded and the point value for each element is identical for anyone using OO for this assignment.
NOTE: there are some great tutorials on working with OpenOffice which can be found in the Content menu. Look for the
Tutorials
menu item in the section under
OpenOffice - Database Alternative for Mac OS X
.
As you recall, data is a collection of facts (numbers, text, even audio and video files) that is processed into usable information. Much like a spreadsheet, a database is a collection of such facts that you can then slice and dice in various ways to extract information or make decisions. However, the advantage and primary use of a database over a spreadsheet is its ability to handle a large volume of data and yet allow for quick access to the information that is desired.
Databases are everywhere now and impact our lives in a multitude of ways. It can accurately be said that “your life is in a database” or, more accurately, in multiple databases, and information about you (a retrieval of facts about you) is easily accessible. Your shopping history, credit history, medical history, even your driving history, is stored in one or more databases.
This exercise will introduce you to the basic building blocks of any database – fields, records, and files (also called tables). Although you will create a database with a single table containing a small amount of data about computer component Providers, the more applicable use of databases involves the creation of many tables linked together with a common field or “key.” Regardless of the size of the database, the data is stored in the same way – in fields which are combined to create a record. And those records are stored in a file or table. The data is entered into the field via a data entry form, and the information is extracted (to answer a particular question or need) via reports and/or queries.
Specific instructions for the project can be found in the table below.
Create a provider database and related reports and queries to capture contact information for potential PC component providers that might be used to purchase the equipment your specified in your MS Word project – the PC specifications..
This Open Office database assignment has the following parts:
a simple database
table
to hold provider contact information; some of the required fields in the table require that a Caption be added to the field characteristics. The Caption will be displayed in the report that is to be generated.
a simple database
form
that can be used to enter data into the database table;
a simp.
Similar to 2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx (20)
Honest Reviews of Tim Han LMA Course Program.pptxtimhan337
Personal development courses are widely available today, with each one promising life-changing outcomes. Tim Han’s Life Mastery Achievers (LMA) Course has drawn a lot of interest. In addition to offering my frank assessment of Success Insider’s LMA Course, this piece examines the course’s effects via a variety of Tim Han LMA course reviews and Success Insider comments.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
Normal Labour/ Stages of Labour/ Mechanism of LabourWasim Ak
Normal labor is also termed spontaneous labor, defined as the natural physiological process through which the fetus, placenta, and membranes are expelled from the uterus through the birth canal at term (37 to 42 weeks
Synthetic Fiber Construction in lab .pptxPavel ( NSTU)
Synthetic fiber production is a fascinating and complex field that blends chemistry, engineering, and environmental science. By understanding these aspects, students can gain a comprehensive view of synthetic fiber production, its impact on society and the environment, and the potential for future innovations. Synthetic fibers play a crucial role in modern society, impacting various aspects of daily life, industry, and the environment. ynthetic fibers are integral to modern life, offering a range of benefits from cost-effectiveness and versatility to innovative applications and performance characteristics. While they pose environmental challenges, ongoing research and development aim to create more sustainable and eco-friendly alternatives. Understanding the importance of synthetic fibers helps in appreciating their role in the economy, industry, and daily life, while also emphasizing the need for sustainable practices and innovation.
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
2. + 7-2
Chapter Objectives
Describe the data normalization process
Perform the data normalization process.
Test tables for irregularities using the data normalization
process.
3. + 7-3
Logical Database Design
The process of deciding how to arrange the attributes of the
entities in the business environment into database structures,
such as the tables of a relational database.
The goal is to create well structured tables that properly reflect
the company’s business environment.
4. + 7-4
Logical Design of Relational
Database Systems
(1) The conversion of E-R diagrams into relational tables.
(2) The data normalization technique.
(3) The use of the data normalization technique to test the
tables resulting from the E-R diagram conversions.
5. + 7-5
The Data Normalization Process
A methodology for organizing attributes into tables so that
redundancy among the nonkey attributes is eliminated.
The output of the data normalization process is a properly
structured relational database.
6. + 7-6
The Data Normalization Technique
Input:
all the attributes that must be incorporated into the
database
a list of all the defining associations between the
attributes (i.e., the functional dependencies).
a means of expressing that the value of one particular
attribute is associated with a single, specific value of
another attribute.
If we know that one of these attributes has a particular
value, then the other attribute must have some other value.
7. 7-7
General Hardware Company Database
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
Office
Number
SALESPERSON
Customer
Number
Customer
Name
Salesperson
Number HQ City
CUSTOMER
Customer
Number
Employee
Number
Employee
Name Title
CUSTOMER EMPLOYEE
Product
Number
Product
Name Unit Price
PRODUCT
Salesperson
Number
Product
Number Quantity
SALES
Office
Number Telephone Size
OFFICE
8. + 7-8
Functional
Dependence
Salesperson Number is the determinant.
The value of Salesperson Number determines the
value of Salesperson Name.
Salesperson Name is functionally dependent on
Salesperson Number.
Salesperson Name
Salesperson Number
9. +
General Hardware Environment:
SALESPERSON and PRODUCT
Salesperson Number
Salesperson Name
Commission Percentage
Year of Hire
Department Number
Manager Name
Product Number
Product Name
Unit Price
Quantity
What are the
functional
dependencies?
7-9
10. + 7-10
General Hardware Environment:
SALESPERSON and PRODUCT
Salesperson Number
Salesperson Name
Commission Percentage
Year of Hire
Department Number
Manager Name
Product Number
Product Name
Unit Price
Quantity
Salesperson Number Salesperson Name
Salesperson Number Commission Percentage
Salesperson Number Year of Hire
Salesperson Number Department Nu mber
Salesperson Number Manager Name
Product Number Product Name
Product Number Unit Price
Department Number Manager Name
Salesperson Number, Product Number Quantity
11. +Full Functional dependency:
If A and B are attributes(columns)of a table, B is fully functionally dependent on A
if B is functionally dependent on A, but not on any proper subset of A.
SalesPerson#--SalesPersonName
Partial Functional Dependency:
If A and B are attributes of a table, B is partially dependent on A if there is some
attribute that can be removed from A and yet the dependency still holds.
SP#, SPName -------> Comm%
Comm% is functionally dependent on a subset of A (SP#, SPName),
namely SP#.
Transitive Functional Dependency:
A , B and C are attributes of a table. If A is functionally dependent on B, and B is
functionally dependent on C, then C is Transitively dependent on A via B.
SP#---->SPName, Comm%, YearOfHire, Office#
Office#---Telephone#
SP# attribute functionally determines Telephone# via Office# attribute.
8/11/2022
13. + 7-13
The Data Normalization Process
Once the attributes are arranged in third normal form, the
group of tables that they comprise is a well-structured
relational database with no data redundancy.
Subsequently R.Boyce and E.F.Codd introduced a stronger
definition of 3NF called Boyce-Codd Normal Form(BCNF).
With the exception of 1NF, all these normal forms are based on
Functional dependencies among the attributes of a table. Higher
normal forms that go beyond BCNF were introduced later such as
Fourth Normal Form (4NF) and Fifth Normal Form (5NF). However
these later normal forms deal with situations that are very rare.
A group of tables is said to be in a particular normal form
if every table in the group is in that normal form.
The data normalization process is progressive.
For example, if a group of tables is in second normal form, it is
also in first normal form.
14. + 7-14
General Hardware Company:
Unnormalized Data
Sales-person
Number Product
Number
Sales-person
Name Commission
Percentage
Year
of
Hire
Depart-ment
Number Manager
Name
Product
Name
Unit
Price Quantity
137 19440
24013
26722
Baker 10 1995 73 Scott Hammer
Saw
Pliers
17.50
26.25
11.50
473
170
688
186 16386
19440
21765
24013
Adams 15 2001 59 Lopez Wrench
Hammer
Drill
Saw
12.95
17.50
32.99
26.25
1745
2529
1962
3071
204 21765
26722
Dickens 10 1998 73 Scott Drill
Pliers
32.99
11.50
809
734
361 16386
21765
26722
Carlyle 20 2001 73 Scott Wrench
Drill
Pliers
12.95
32.99
11.50
3729
3110
2738
SALESPERSON/PRODUCT Table
Records contain multivalued attributes.
15. 7-15
General Hardware Company: First
Normal Form
The only thing that is required for a table to be in 1NF is to
contain only atomic values (intersection of each row and
column should contain one and only one value). This is
sometimes referred to as: Eliminate Repeating groups.
The attributes under consideration have been listed in one
table, and a primary key has been established.
The number of records has been increased so that every
attribute of every record has just one value.
The multivalued attributes have been eliminated.
Sales-person
Number
Product
Number
Sales-person
Name
Commission
Percentage
Year
of
Hire
Depart-ment
Number
Manager
Name
Product
Name
Unit
Price
Quantity
SALESPERSON/PRODUCT Table
16. + 7-16
General Hardware Company: First
Normal Form
Sales-person
Number Product
Number
Sales-person
Name Commission
Percentage
Year
of
Hire
Depart-ment
Number Manager
Name
Product
Name
Unit
Price Quantity
137 19440 Baker 10 1995 73 Scott Hammer 17.50 473
137 24013 Baker 10 1995 73 Scott Saw 26.25 170
137 26722 Baker 10 1995 73 Scott Pliers 11.50 688
186 16386 Adams 15 2001 59 Lopez Wrench 12.95 1745
186 19440 Adams 15 2001 59 Lopez Hammer 17.50 2529
186 21765 Adams 15 2001 59 Lopez Drill 32.99 1962
186 24013 Adams 15 2001 59 Lopez Saw 26.25 3071
204 21765 Dickens 10 1998 73 Scott Drill 32.99 809
204 26722 Dickens 10 1998 73 Scott Pliers 11.50 734
361 16386 Carlyle 20 2001 73 Scott Wrench 12.95 3729
361 21765 Carlyle 20 2001 73 Scott Drill 32.99 3110
361 26722 Carlyle 20 2001 73 Scott Pliers 11.50 2738
SALESPERSON/PRODUCT Table
17. + 7-17
General Hardware Company: First
Normal Form
First normal form is merely a starting point in
the normalization process.
First normal form contains a great deal of
data redundancy.
Three records involve salesperson 137, so there
are three places in which his name is listed as
Baker, his commission percentage is listed as 10,
and so on.
Two records involve product 19440 and this
product’s name is listed twice as Hammer and its
unit price is listed twice as 17.50.
18. + 7-18
Second Normal Form
A Table is said to be in 2NF if it is in 1NF and there are no
partial dependencies
No Partial Functional Dependencies
Every non primary key attribute of the table must be fully functionally
dependent on the entire primary key of that table.
A non-key attribute cannot depend on only part of the key.
19. 7-19
General Hardware Company: Second
Normal Form
Salesperson
Number
Product
Number
Quantity
QUANTITY Table
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year
of
Hire
Department
Number
Manager
Name
SALESPERSON Table
In SALESPERSON, Salesperson Number is the sole primary
key attribute. Every nonkey attribute of the table is fully defined
just by Salesperson Number.
Similar logic for PRODUCT and QUANTITY tables.
Product
Number
Product
Name
Unit
Price
PRODUCT Table
20. 7-20
General Hardware Company: Second
Normal Form
Product
Number
Product
Name
Unit
Price
16386 Wrench 12.95
19440 Hammer 17.50
21765 Drill 32.99
24013 Saw 26.25
26722 Pliers 11.50
PRODUCT Table
Salesperson
Number
Product
Number Quantity
137 19440 473
137 24013 170
137 26722 688
186 16386 1745
186 19440 2529
186 21765 1962
186 24013 3071
204 21765 809
204 26722 734
361 16386 3729
361 21765 3110
361 26722 2738
QUANTITY Table
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year
of
Hire
Department
Number
Manager
Name
137 Baker 10 1995 73 Scott
186 Adams 15 2001 59 Lopez
204 Dickens 10 1998 73 Scott
361 Carlyle 20 2001 73 Scott
SALESPERSON Table
21. + 7-21
Third Normal Form
A Table that is in 1NF and 2NF and in which no non primary
key attribute is transitively dependent on the primary key.
Does not allow transitive dependencies in which one nonkey
attribute is functionally dependent on another.
Nonkey attributes are not allowed to define other nonkey
attributes.
"Each attribute must be a fact about the key, the whole key, and
nothing but the key."
22. 7-22
General Hardware Company: Third
Normal Form
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year of
Hire
Department
Number
SALESPERSON Table
Department
Number
Manager
Name
DEPARTMENT Table
Product
Number
Product
Name
Unit
Price
PRODUCT Table
Salesperson
Number
Product
Number
Quantity
QUANTITY Table
23. 7-23
General Hardware Company: Third
Normal Form
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year of
Hire
Department
Number
137 Baker 10 1995 73
186 Adams 15 2001 59
204 Dickens 10 1998 73
361 Carlyle 20 2001 73
SALESPERSON Table
Department
Number
Manager
Name
59 Lopez
73 Scott
DEPARTMENT Table
Product
Number
Product
Name
Unit
Price
16386 Wrench 12.95
19440 Hammer 17.50
21765 Drill 32.99
24013 Saw 26.25
26722 Pliers 11.50
PRODUCT Table
Salesperson
Number
Product
Number Quantity
137 19440 473
137 24013 170
137 26722 688
186 16386 1745
186 19440 2529
186 21765 1962
186 24013 3071
204 21765 809
204 26722 734
361 16386 3729
361 21765 3110
361 26722 2738
QUANTITY Table
24. + 7-24
General Hardware Company: Third
Normal Form
Important points about the third normal form
structure are:
It is completely free of data redundancy.
All foreign keys appear where needed to logically
tie together related tables.
It is the same structure that would have been
derived from a properly drawn entity-relationship
diagram of the same business environment.
25. +
Recap + clarification
0NF:
Unstructured data, can have multi-valued attributes
1NF:
Atomic values (one per column of the record)
No duplicate rows (implies there is a key)
As we move forward need to consider functional dependencies
and determine candidate keys
Note: earlier slides simplified this slightly by saying choose a
primary key, but normalization is actually about candidate keys
For the higher forms of normalization, we need to consider the
case where there is not a single option for the primary key
8/11/2022
26. +
Definitions
Superkey: a combination of attributes that can be used to
uniquely identify a row in a database. The trivial superkey is all
attributes.
Candidate key: a minimal superkey – all attributes are
necessary to uniquely identify the record
Primary key: one candidate key, arbitrarily chosen
Prime attribute: an attribute that occurs in some candidate key
Non prime attribute: an attribute that does not occur in any
candidate key
8/11/2022
27. +
2NF (revisited)
A Table is said to be in 2NF if it is in 1NF and there are no
partial dependencies
No Partial Functional Dependencies
Every non primary key attribute of the table must be fully functionally
dependent on the entire primary key of that table.
A non-key attribute cannot depend on only part of the key.
No Partial Functional Dependences
Every non prime key attribute of the table must be fully functionally
dependent on the entire key of one of the candidate keys in the
table.
An non-prime attribute cannot depend on only part of one of the
candidate keys.
8/11/2022
28. +
3NF revisited
A Table that is in 1NF and 2NF and in which no non primary
key attribute is transitively dependent on the primary key.
Old:
Does not allow transitive dependencies in which one non-key
attribute is functionally dependent on another.
Nonkey attributes are not allowed to define other nonkey attributes.
New:
Every non-prime attribute is non-transitively dependent on every
candidate key in the table.
The attributes that do not directly contribute to the description of the
candidate keys are removed from the table. In other words, no
transitive dependency is allowed.
8/11/2022
29. +
"Each non-key attribute must
provide a fact about the key, the
whole key, and nothing but the key.”
The key: 1NF – we have a table of related items, with each row
unique, with atomic values
The whole key: 2NF – no partial dependences on the candidate
keys
Nothing but the key: 3NF – no transitive dependencies
8/11/2022
30. + 7-30
Boyce-codd Normal Form (BCNF)
A Table is in BCNF if and only if every determinant (i.e., the
attribute or a group of attributes on which some other
attribute is fully functionally dependent) is a candidate key.
BCNF is a stronger form of 3NF.
The difference between 3NF and BCNF is that for a
Functional dependency A--->B, 3NF allows this
dependency in a table if attribute B is a primary key
attribute and attribute A is not a candidate key, where as
BCNF insists that for this dependency to remain in a table,
attribute A must be a candidate key.
Only in rare cases does a 3NF table not meet the
requirements of BCNF. A 3NF table which does not have
multiple overlapping candidate keys is guaranteed to be in
BCNF. Depending on what its functional dependencies are,
a 3NF table with two or more overlapping candidate keys
may or may not be in BCNF
31. + Example of 3NF table not in BCNF
Today's Court
Bookings
Each row in the table represents a court booking at a tennis club that
has one hard court (Court 1) and one grass court (Court 2). A booking is
defined by its Court and the period for which the Court is reserved
Additionally, each booking has a Rate Type associated with it. There
are four distinct rate types:
SAVER, for Court 1 bookings made by members
STANDARD, for Court 1 bookings made by non-members
PREMIUM-A, for Court 2 bookings made by members
PREMIUM-B, for Court 2 bookings made by non-members
http://en.wikipedia.org/wiki/Boyce%E2%80%93Codd_normal_form 8/11/2022
Court StartTime EndTime RateType
1 09:30 10:30 SAVER
1 11:00 12:00 SAVER
1 14:00 15:30 STANDARD
2 10:00 11:30 PREMIUM-B
2 11:30 13:30 PREMIUM-B
2 15:00 16:30 PREMIUM-A
32. +
What is the problem?
Identify the functional dependencies
Identify the table’s super keys
Determine the candidate keys
Why isn’t the table in BCNF?
A Table is in BCNF if and only if every determinant is a candidate
key.
For all functional dependencies A -> B, is A a candidate key?
8/11/2022
33. +
Fourth Normal Form (4NF)
4NF is a stronger normal form than 3NF/BCNF as it prevents
Tables from containing nontrivial Multi-Valued Dependencies
(MVDs) and hence data redundancy.
The Normalization of BCNF Tables to 4NF involves the removal
of MVDs from the Table by placing the attribute(s) in a new
Table along with the copy of the determinant(s).
http://en.wikipedia.org/wiki/Fourth_normal_form
8/11/2022
34. +
Pizza Delivery Example – not in 4NF
Restaurant Pizza Variety Delivery Area
A1 Pizza Thick Crust Springfield
A1 Pizza Thick Crust Shelbyville
A1 Pizza Thick Crust Capital City
A1 Pizza Stuffed Crust Springfield
A1 Pizza Stuffed Crust Shelbyville
A1 Pizza Stuffed Crust Capital City
Elite Pizza Thin Crust Capital City
Elite Pizza Stuffed Crust Capital City
Vincenzo's Pizza Thick Crust Springfield
Vincenzo's Pizza Thick Crust Shelbyville
Vincenzo's Pizza Thin Crust Springfield
Vincenzo's Pizza Thin Crust Shelbyville
8/11/2022
35. +
Fifth Normal Form (5NF)
Also known as project-join normal form (PJ/NF)
Designed to reduce redundancy in relational databases
recording multi-valued facts by isolating semantically related
multiple relationships.
A table is said to be in the 5NF if and only if every join
dependency in it is implied by the candidate keys.
http://en.wikipedia.org/wiki/Fifth_normal_form
8/11/2022
36. +
Traveling Salesman Product Availability By Brand
Traveling Salesman Brand Product Type
Jack Schneider Acme Vacuum Cleaner
Jack Schneider Acme Breadbox
Willy Loman Robusto Pruning Shears
Willy Loman Robusto Vacuum Cleaner
Willy Loman Robusto Breadbox
Willy Loman Robusto Umbrella Stand
Louis Ferguson Robusto Vacuum Cleaner
Louis Ferguson Robusto Telescope
Louis Ferguson Acme Vacuum Cleaner
Louis Ferguson Acme Lava Lamp
Louis Ferguson Nimbus Tie Rack
8/11/2022
Not in 5NF if the Salesman must offer only products of Type
P made by Brand B if that product type and brand is in his
repetoire
38. +
Other good resources:
http://www.informationqualitysolutions.com/FreeStuff/rettigNor
malizationPoster.pdf
Today’s handout includes the explanations of each
normalization step for the example highlighted in the poster
8/11/2022
39. 7-39
General Hardware Company:
Functional Dependencies
Salesperson Number Salesperson Name
Salesperson Number Commission Percentage
Salesperson Number Year of Hire
Salesperson Number Department Nu mber
Salesperson Number Manager Name
Customer Number Customer Name
Customer Number Salesperson Number
Customer Number HQ City
Customer Number, Employee Number Employee Name
Customer Number, Employee Number Title
Product Number Product Name
Product Number Unit Price
Department Number Manager Name
Salesperson Number, Product Number Quantity
Office Number Telephone
Office Number Salesperson Number
Office Number Size
40. 7-40
General Hardware Company: First
Normal Form
Salesperson
Number
Customer
Number
Employee
Number
Product
Number
Office
Number
Salesperson
Name
Commission
Percentage
Year
of
Hire
Department
Number
Manager
Name
Customer
Name HQ
City
Employee
Name Title
Product
Name
Unit
Price Quantity Telephone Size
41. + 7-41
World Music Association: Functional
Dependencies
Orchestra Name City
Orchestra Name Country
Orchestra Name Music Director
Musician Number Musician Name
Musician Number Instrument
Musician Number Annual Salary
Musician Number Orchestra Name
Musician Number, Degree Univeristy
Musician Number, Degree Year
Composer Name Country
Composer Name Date of Birth
Composition Name, Composer Name Year
Orchestra Name, Composition Name, Composer Name Year
Orchestra Name, Composition Name, Composer Name Price
42. + 7-42
Lucky Rent-A-Car:
Functional Dependencies
Manufacturer Name Manufacturer Country
Manufacturer Name Sales Rep Na me
Manufacturer Name Sales Rep Te lephone
Car Serial Number Model
Car Serial Number Year
Car Serial Number Class
Car Serial Number Manufacturer Na me
Repair Number Car Serial Number
Repair Number Date
Repair Number Procedure
Repair Number Mileage
Repair Number Repair Time
Customer Number Customer Name
Customer Number Customer Address
Customer Number Customer Telephone
Car Serial Number, Customer Number, Rental Date Return Date
Car Serial Number, Customer Number, Rental Date Total Cost