Professional Documents
Culture Documents
A. Fragmentation: Multivalued Dependency
A. Fragmentation: Multivalued Dependency
Fragmentation
Fragmentation is the task of dividing a table into a set of smaller tables. The subsets of the
table are called fragments. Fragmentation can be of three types: horizontal, vertical, and
hybrid (combination of horizontal and vertical). Horizontal fragmentation can further be
classified into two techniques: primary horizontal fragmentation and derived horizontal
fragmentation.
Types –
Vertical Fragmentation
In vertical fragmentation, the fields or columns of a table are grouped into fragments. In order
to maintain reconstructiveness, each fragment should contain the primary key field(s) of the
table. Vertical fragmentation can be used to enforce privacy of data.
Horizontal Fragmentation
Horizontal fragmentation groups the tuples of a table in accordance to values of one or more
fields. Horizontal fragmentation should also confirm to the rule of reconstructiveness. Each
horizontal fragment must have all columns of the original base table.
Hybrid Fragmentation
In hybrid fragmentation, a combination of horizontal and vertical fragmentation techniques
are used. This is the most flexible fragmentation technique since it generates fragments with
minimal extraneous information. However, reconstruction of the original table is often an
expensive task.
Multivalued Dependency
Multivalued dependency occurs when two attributes in a table are independent of each
other but, both depend on a third attribute.
A multivalued dependency consists of at least two attributes that are dependent on a third
attribute that's why it always requires at least three attributes.
c. Locking-
Locking protocols are used in database management systems as a means of concurrency control.
Multiple transactions may request a lock on a data item simultaneously. Hence, we require a
mechanism to manage the locking requests made by transactions. Such a mechanism is called as
Lock Manager. It relies on the process of message passing where transactions and lock manager
exchange messages to handle the locking and unlocking of data items.
Indexed sequential access method (ISAM)
ISAM method is an advanced sequential file organization. In this method, records are stored
in the file using the primary key. An index value is generated for each primary key and
mapped with the record. This index contains the address of the record in the file.
Pros of ISAM:
In this method, each record has the address of its data block, searching a record in a
huge database is quick and easy.
This method supports range retrieval and partial retrieval of records. Since the index
is based on the primary key values, we can retrieve the data for the given range of
value. In the same way, the partial value can also be easily searched, i.e., the student
name starting with 'JA' can be easily searched.
Cons of ISAM
This method requires extra space in the disk to store the index value.
When the new records are inserted, then these files have to be reconstructed to
maintain the sequence.
When the record is deleted, then the space used by it needs to be released. Otherwise,
the performance of the database will slow down.
4.b>RDBMS vS DBMS
DBMS RDBMS
The relationship between two tables The relationship between two tables
or files maintain by the program. or files specified at the time of table
operation.
It doesn’t support client server It support client server architecture.
architecture.
There is no security of data. Its has multiple level of security
It doesn’t support distributed Supports distributed database.
database
Each table is given an extension. Many table are grow up in one
database.
A .Difference between Physical and Logical Data Independence :
e.
c. Transaction State
1. Active- It define the state of transaction.
2. Partial Commmited- After the last statement Have been
executed then the state is executed.
3. Commited- Define the the successful execution is
completed.
4. Failed- When normal execution can no longer process then
its executed.
5. Abort- After The transaction have been rolled back and the
db restored to its state and prior to the start of transaction
then the state is executed.