Interpreting and Building Entity-Relationship Diagram (ERD) MIS 605 GCU
docx
keyboard_arrow_up
School
Oral Roberts University *
*We aren’t endorsed by this school
Course
605
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
2
Uploaded by AdmiralFieldLion3
Part 1:
For this part of the assignment, you will use the "AdventureWorks 2014 OLTP
Database," located in the Class Resources, and use the schema. Follow the tree/chain
to answer the questions below in a Microsoft Word document.
1.
How does the Sales.SalesTerritory table relate to the Person.StateProvince
table? Which table holds the Primary and the Foreign Key? On what field do
they join together?
The Sales.SalesTerritory table includes a foreign key connected to the primary key
of the Person.StateProvince table. The Person.StateProvince table contains the
primary key for the state or province, and the foreign key is Sales.SalesTerritory
connected to it. They join together in the TerritoryID field.
2.
If you wanted to know the Planned Cost of a Product, what route would you
take to the data? Identify the tables and fields used to join on each.
The route is to examine tables associated with product details and prices. The
tables used for each join are Production.Product and
Production.ProductCostHistory. The fields include ProductID and ModifiedDate.
3.
Imagine a bonus was paid to an employee using a different currency. Identify
the fields you would need so you could access the information. List all the
tables involved, and the fields used to join.
Look at tables pertaining to employee details, incentive payments, and currency
rate changes. The fields are the EmployeeID on both Employee and
EmployeePayHistory and CurrencyRateDate and ToCurrencyCode in
CurrencyRate. The tables involve Sales.CurrencyRate,
HumanResources.EmployeePayHistory, and HumanResources.Employee.
Part 2:
In a one to two paragraph Word document, explain how these fields relate to the
rest of the database content.
The inclusion of the EmergecyContact table in the Adventure Works Cycles
database greatly improves the overall data management system, offering insightful
information about employees'
emergency contact information.
The
BusinessEntityID field establishes a one-and-many table relationship between the
HumanResources.Employee and the most recent EmergencyContact. The fields in
the EmergencyContact table, such as Name, PhoneNumber, Relationship etc, add
crucial data to the database, enabling thorough evaluations of different contact
information and supporting the process of making reasonable choices about
employee emergency information. Adding the EmergencyContact table to the
database improves its overall HR information capabilities by providing a thorough
overview of an employee's emergency contact information in the context of the
company.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help