See Description

Assignment #7

Instruction for properly completing the assignment:

Due Sunday of Week 7 by 11:55 PM [5% of your grade]

1. Download the attached template called "INFO620-Assignment7_LastNameFirst.doc".
2. Change the file name applying your Last Name and First Name in place of the LastNameFirst.
3. Then open the newly saved file and enter your name and the date due on the top of the document.
4. Then enter each problem's solution within this same file in their proper locations WITHOUT changing or erasing the questions.
5. Support your responses and answers by references from the text.
6. Review and complete all questions.
7. Then upload to Assignment #7 area of the Assignments.
8. Your grade may be reduced if these instructions are NOT followed closely.

Week 7 Assignment Grading Rubric: 

Here are the contents of Assignment #7 (however - please use the template attached  - don't copy and paste from here):

CH20: PHYSICAL DATABASE DESIGN AND TUNING

#20.5 – Under what situations would denormalization of a database schema be used? Give examples of denormalization.

#20.8 – Illustrate the types of changes to SQL queries that may be worth considering for improving the performance during database tuning.

CH 21: INTRODUCTION TO TRANSACTION PROCESSING CONCEPTS and THEORY

#21.14 - Change transaction T 2 in Figure 21.2b to read:

read_item(X);

X:= X+M;

if X > 90 then exit

else write_item(X);

Discuss the final result of the different schedules in Figure 21.3 (a) and (b), where M = 2 and N = 2, with respect to the following questions. Does adding the above condition change the final outcome? Does the outcome obey the implied consistency rule (that the capacity of X is 90)?

#21.18 - How many serial schedules exist for the three transactions in Figure 21.8 (a)? What are they? What is the total number of possible schedules?

#21.20 - Why is an explicit transaction end statement needed in SQL but not an explicit begin statement?

CH 22: CONCURRENCY CONTROL TECHNIQUES

#22.22 - Prove that strict two-phase locking guarantees strict schedules.

#22.26 - Repeat Exercise 22.25, but use the multi-version timestamp ordering method.