Consider the database schema of Question3, suggest at least two different types of users for the system. You may use my_account view for one of the users. Create an authorization matrix for the relations. Make suitable assumptions, if any.

What is a deadlock? How can you detect deadlock? Explain with the help of a wait for graph. What are the possibilities that the deposit and withdrawal transactions as created in part (iii) will result into deadlock? Explain your answer.

Compare and contrast the two tier model to that of 3 tier model client server architecture. Can you implement the database given in question 3 as a 3 tier model? Explain your answer.

Create the relations from the E-R diagram that you have drawn for part (ii). The relations must be at least in 2NF. You must do the following with the relations

1. Enter about 5 sets of meaningful data in each of the relations
2. Identify the domain of various attributes
3. Identify the primary keys of all the relations
4. Identify the foreign keys and referential integrity constraints integrity constraints in the relations.

Now, assume that the bank schema as given in Question 3 is being implemented using distributed database. Suggest suitable data fragmentation needed for this distributed database.

What are the problems associated with data Redundancy in a relation? How can you solve those problems? Can referential integrity constraints help in addressing those problem? Give reasons in support of your answer.

Perform the following queries using SQL for the relations of part(i):

1. Find the list of the account holders whose account balance is less than Rs.1000/-
2. Find the details of those account holders who have withdrawal nore than Rs.1,00,000/- in the last month.
3. Find the sum of deposits that has been credited in each account in the last year.
4. Find an account holder who has not withdrawn any money in the last year.