Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions 02_assignments/design_a_logical_model.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Assignment 1: Design a Logical Model

The ERD and the customer_address tables are attached to the pull request.

## Question 1
Create a logical model for a small bookstore. 📚

Expand All @@ -15,15 +17,15 @@ _Hint, search type 1 vs type 2 slowly changing dimensions._

Bonus: Are there privacy implications to this, why or why not?
```
Your answer...
The architecture that will overwrite is type 1, and the architecture that will retain changes is type 2. There are privacy implications to the use of type 2 slowly changing dimensions where changes are retained. The bookstore keeps track of how a customer’s address has changed over time. This is an unnecessary violation of privacy when only the current address is really needed for the bookstore’s database.
```

## Question 4
Review the AdventureWorks Schema [here](https://i.stack.imgur.com/LMu4W.gif)

Highlight at least two differences between it and your ERD. Would you change anything in yours?
```
Your answer...
The entities of the AdventureWorks schema are categorized by department. Also, there is a dbo schema that contains a build version table, a database log table, and an error log table. The build version table contains the current version number of the database. The database log table tracks all changes made to the database. The error log table tracks all errors in the database. Implementing these two changes to the bookstore ERD would be beneficial.
```

# Criteria
Expand Down