Murach's SQL Server 2019 for Developers Create an Entity Relationship diagram using Visio or visual-paradigm or Lucidchart or other sources. You will look at page 313 of your textbook and recreate the middle example that includes the Employees, Membership, and Committees tables.

Database System Concepts
7th Edition
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Chapter1: Introduction
Section: Chapter Questions
Problem 1PE
icon
Related questions
Question
Murach's SQL Server 2019 for Developers Create an Entity Relationship diagram using Visio or visual-paradigm or Lucidchart or other sources. You will look at page 313 of your textbook and recreate the middle example that includes the Employees, Membership, and Committees tables.
●
●
●
●
●
The relationships between the tables in the accounts payable system
Vendors
VendorID
VendorName
VendorAddress
Vendor City
Vendor State
VendorZipCode
VendorPhone
Vendor ContactFName
Vendor ContactLName
Terms
Account No
Employees
EmployeelD
FirstName
LastName
Invoices
InvoicelD
VendorID
EmployeelD
CommitteelD
Employees
EmployeelDe
FirstName
LastName
InvoiceNumber
Invoice Date
Invoice Total
Two tables with a many-to-many relationship
Memberships
Payment Total
CreditTotal
Terms
InvoiceDueDate
Payment Date
Account No
Linking table
Chapter 10 How to design a database
Two tables with a one-to-one relationship
Employee Photos
EmployeelD
EmployeePhoto
InvoiceLineltems
InvoicelD
InvoiceSequence
AccountNo
Lineltem Description
ItemQuantity
Description
Most tables should have a primary key that uniquely identifies each row. If
necessary, you can use a composite key that uses two or more columns to uniquely
identify each row.
Item UnitPrice
LineltemAmount
Committees
CommitteelD
CommitteeName
The values of the primary keys should seldom, if ever, change. The values should
also be short and easy to enter correctly.
If two tables have a many-to-many relationship, you'll need to define a linking
table to relate them. Then, each of the tables in the many-to-many relationship will
have a one-to-many relationship with the linking table. The linking table doesn't
usually have a primary key.
If two tables have a one-to-one relationship, they should be related by their primary
keys. This type of relationship is typically used to improve performance. Then,
columns with large amounts of data can be stored in a separate table.
Figure 10-5 How to identify the primary and foreign keys
If a suitable column doesn't exist, you can create an identity column that can be
used as the primary key.
If two tables have a one-to-many relationship, you may need to add a foreign key
column to the table on the "many" side. The foreign key column must have the
same data type as the primary key column it's related to.
313
Transcribed Image Text:● ● ● ● ● The relationships between the tables in the accounts payable system Vendors VendorID VendorName VendorAddress Vendor City Vendor State VendorZipCode VendorPhone Vendor ContactFName Vendor ContactLName Terms Account No Employees EmployeelD FirstName LastName Invoices InvoicelD VendorID EmployeelD CommitteelD Employees EmployeelDe FirstName LastName InvoiceNumber Invoice Date Invoice Total Two tables with a many-to-many relationship Memberships Payment Total CreditTotal Terms InvoiceDueDate Payment Date Account No Linking table Chapter 10 How to design a database Two tables with a one-to-one relationship Employee Photos EmployeelD EmployeePhoto InvoiceLineltems InvoicelD InvoiceSequence AccountNo Lineltem Description ItemQuantity Description Most tables should have a primary key that uniquely identifies each row. If necessary, you can use a composite key that uses two or more columns to uniquely identify each row. Item UnitPrice LineltemAmount Committees CommitteelD CommitteeName The values of the primary keys should seldom, if ever, change. The values should also be short and easy to enter correctly. If two tables have a many-to-many relationship, you'll need to define a linking table to relate them. Then, each of the tables in the many-to-many relationship will have a one-to-many relationship with the linking table. The linking table doesn't usually have a primary key. If two tables have a one-to-one relationship, they should be related by their primary keys. This type of relationship is typically used to improve performance. Then, columns with large amounts of data can be stored in a separate table. Figure 10-5 How to identify the primary and foreign keys If a suitable column doesn't exist, you can create an identity column that can be used as the primary key. If two tables have a one-to-many relationship, you may need to add a foreign key column to the table on the "many" side. The foreign key column must have the same data type as the primary key column it's related to. 313
Expert Solution
steps

Step by step

Solved in 3 steps with 1 images

Blurred answer
Knowledge Booster
Arrays
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
  • SEE MORE QUESTIONS
Recommended textbooks for you
Database System Concepts
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
C How to Program (8th Edition)
C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Programmable Logic Controllers
Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education