Scribd
Upload
7 views

Lecture 5

This document discusses distributed database systems and semantic data control including view management, security control, and integrity control. It describes how views are defined and can be manipulated similarly to base relations. Materialized views can improve performance by storing view results but require maintenance when the base data changes.

Uploaded by

Mostafa Elrashidy
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
7 views

Lecture 5

This document discusses distributed database systems and semantic data control including view management, security control, and integrity control. It describes how views are defined and can be manipulated similarly to base relations. Materialized views can improve performance by storing view results but require maintenance when the base data changes.

Uploaded by

Mostafa Elrashidy
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Distributed Database Systems

© 2020, M.T. Özsu & P. Valduriez 1


Semantic Data Control

◼ Involves:
❑ View management
❑ Security control
❑ Integrity control

◼ Objective :
❑ Ensure that authorized users perform correct operations on the
database, contributing to the maintenance of the database
integrity.

© 2020, M.T. Özsu & P. Valduriez 2


View Management

View – virtual relation EMP


❑ generated from base relation(s) by a query ENO ENAME TITLE
❑ not stored as base relations E1 J. Doe Elect. Eng
E2 M. Smith Syst. Anal.
Example : E3 A. Lee Mech. Eng.
CREATE VIEW SYSAN(ENO,ENAME) E4 J. Miller Programmer
E5 B. Casey Syst. Anal.
AS SELECT ENO,ENAME E6 L. Chu Elect. Eng.
FROM EMP E7 R. Davis Mech. Eng.
E8 J. Jones Syst. Anal.
WHERE TITLE= "Syst. Anal."

3
View Management

Views can be manipulated as base relations

Example :

SELECT ENAME, PNO, RESP


FROM SYSAN, ASG
WHERE SYSAN.ENO = ASG.ENO

4
Query Modification

Queries expressed on views

Queries expressed on base relations


Example :
SELECT ENAME, PNO, RESP
FROM SYSAN, ASG
WHERE SYSAN.ENO = ASG.ENO

SELECT ENAME,PNO,RESP
FROM EMP, ASG
WHERE EMP.ENO = ASG.ENO
AND TITLE = "Syst. Anal."

5
View Management

◼ To restrict access
CREATE VIEW ESAME
AS SELECT *
FROM EMP E1, EMP E2
WHERE E1.TITLE = E2.TITLE
AND E1.ENO = USER
◼ Query
SELECT *
FROM ESAME

6
View Updates

◼ Updatable
CREATE VIEW SYSAN(ENO,ENAME)
AS SELECT ENO,ENAME
FROM EMP
WHERE TITLE="Syst. Anal."

◼ Non-updatable
CREATE VIEW EG(ENAME,RESP)
AS SELECT ENAME,RESP
FROM EMP, ASG
WHERE EMP.ENO=ASG.ENO

7
View Management in Distributed DBMS

◼ Views might be derived from fragments.


◼ View definition storage should be treated as database
storage
◼ Query modification results in a distributed query
◼ View evaluations might be costly if base relations are
distributed
❑ Use materialized views

8
Materialized View

◼ Origin: snapshot in the 1980’s


❑ Static copy of the view, avoid view derivation for each query
❑ But periodic recomputing of the view may be expensive
◼ Actual version of a view
❑ Stored as a database relation, possibly with indices
◼ Used much in practice
❑ DDBMS: No need to access remote, base relations
❑ Data warehouse: to speed up OLAP
◼ Use aggregate (SUM, COUNT, etc.) and GROUP BY

9
Materialized View Maintenance

◼ Process of updating (refreshing) the view to reflect


changes to base data
❑ Resembles data replication but there are differences
◼ View expressions typically more complex
◼ Replication configurations more general
◼ View maintenance policy to specify:
❑ When to refresh
❑ How to refresh

10
When to Refresh a View

◼ Immediate mode
❑ As part of the updating transaction, e.g. through 2PC
❑ View always consistent with base data and fast queries
❑ But increased transaction time to update base data
◼ Deferred mode (preferred in practice)
❑ Through separate refresh transactions
◼ No penalty on the updating transactions
❑ Triggered at different times with different trade-offs
◼ Lazily: just before evaluating a query on the view
◼ Periodically: every hour, every day, etc.
◼ Forcedly: after a number of predefined updates

11
How to Refresh a View

◼ Full computing from base data


❑ Efficient if there has been many changes
◼ Incremental computing by applying only the changes to
the view
❑ Better if a small subset has been changed
❑ Uses differential relations which reflect updated data only

12
Differential Relations

Given relation R and update u


R+ contains tuples inserted by u
R- contains tuples deleted by u
Type of u
insert R- empty
delete R+ empty
modify R+  (R – R- )
Refreshing a view V is then done by computing
V+  (V – V- )
computing V+ and V- may require accessing base data

13
Example

EG = SELECT DISTINCT ENAME, RESP


FROM EMP, ASG
WHERE EMP.ENO=ASG.ENO

EG+= (SELECT DISTINCT ENAME, RESP


FROM EMP, ASG+
WHERE EMP.ENO=ASG+.ENO) UNION
(SELECT DISTINCT ENAME, RESP
FROM EMP+, ASG
WHERE EMP+.ENO=ASG.ENO) UNION
(SELECT DISTINCT ENAME, RESP
FROM EMP+, ASG+
WHERE EMP+.ENO=ASG+.ENO)

14
15
16
17
18
19
Counting Algorithm

◼ Basic idea
❑ Maintain a count of the number of derivations for each tuple in
the view
❑ Increment (resp. decrement) tuple counts based on insertions
(resp. deletions)
❑ A tuple in the view whose count is zero can be deleted
◼ Algorithm
1. Compute V+ and V- using V, base relations and diff. relations
2. Compute positive in V+ and negative counts in V-
3. Compute V+  (V – V- ), deleting each tuple in V with count=0
◼ Optimal: computes exactly the view tuples that are
inserted or deleted
© 2020, M.T. Özsu & P. Valduriez 20

You might also like