Entity
Attribute
Relationship
Notation
A. Entity
Centralized control of data
Data independence
Both A and B
Neither A nor B
Relations
Queries
Domains
All of the above
2NF
5NF
4NF
3NF
Selection operator.
Projection operator.
Aggregation operators.
Division operator.
distinct values
cannot have NULL
both (A) & (B)
same as primary key
Conceptual, physical and internal
Conceptual, view and external
Logical, physical and internal
Logical, physical and view
add an attribute
delete an attribute
alter the default values of an attribute
all of the above
theta join
outer join
natural join
composed join
Entity set
File
Entity instance
Organization
Query languages and utilities
DML and query language
Data dictionary and transaction log
Data dictionary and query language
Deferred update
Immediate update
Two-phase commit
Shadow paging
Similarity
Granularity
Dimensionality
Arity
partially committed
active
committed
none of the above
Serializable schedule.
Recoverable schedule.
Deadlock free schedule.
Cascadeless schedule.
Query
Embedded SQL
DDL
DCL
Functional dependency
Multi-valued dependency
Transitive dependency
Partial dependency
repeatable read
read committed
read uncommitted
serializable
weak entity sets
weak relationship sets
strong entity sets
strong relationship sets
UPDATE S CITY = KANPUR WHERE SNO=S1
UPDATE S SET CITY = KANPUR FOR SNO=S1
UPDATE S SET CITY = KANPUR WHERE SNO=S1
UPDATE S RENAME CITY = KANPUR WHERE SNO=S1
Commutative
Associative
idempotent
distributive
All views are not updateable
The views may be referenced in an SQL statement whenever tables are referenced.
The views are instantiated at the time they are referenced and not when they are defined.
The definition of a view should not have GROUP BY clause in it.
No functional dependencies (FDs) exist.
No multivalued dependencies (MVDs) exist.
No partial FDs exist.
No partial MVDs exist.
Fields
Records
Relations
Keys
left outer join
right outer join
full outer join
inner join
Recovery measures.
Security measures.
Concurrency measures.
uthorization measures.
A database design may be ambiguous.
It should avoid/reduce the redundancy.
Unrelated data should be in the same table so that updating the data will be easy.
An entity should not have attributes.
authorization and integrity manager
buffer manager
transaction manager
file manager
Two - phase locking
Graph-based locking
Time-stamp based locking
None of these .
Relation
Tuple
Database
Domain
With finer degree of granularity of locking a high degree of concurrency is possible.
Locking prevents non-serializable schedules.
Locking cannot take place at field level.
An exclusive lock on data item X is granted even if a shared lock is already held on X.