Create a table for customers. The manager tells me that this table needs to track the following information: all customers' social security number, first and last name, address, city, state and zip code, email, phone number, birth date, and date of applying for a library card. Your task is to first "sketch" a customer table (basically what data items or columns should be included in the table) using the Customer_information table at background section as an example. The table should contain the following:
Design one more table: Customer checkout table to track the books and CDs that the customer has checked out from the library. Customers and Customer Checkout table are related to one another.
The Customer Checkout table contains the data for each book. The primary key consists of two pieces of data: Checkout number and customer number. One customer can check out 1 or more books/CDs at a time, but only one customer on a check out order.
If I were to draw an ER diagram of my complete design for the community library, I could use Visio, or Microsoft word feature to draw the chart, or write down the table schemata and describe the relationships among them.
Talk about this experience.
I have attached two documents. The document named ...
The expert designs one more table database modeling and ER diagrams.