Database Management System Vs File Management System

A Database Management System (DMS) is a combination of computer software, hardware,

and information designed to electronically manipulate data via computer processing. Two
types of database management systems are DBMSs and FMSs. In simple terms, a File
Management System (FMS) is a Database Management System that allows access to single
files or tables at a time. FMSs accommodate flat files that have no relation to other files.
The FMS was the predecessor for the Database Management System (DBMS), which allows
access to multiple files or tables at a time (see Figure 1 below)

File Management Systems

Advantages
Disadvantages
Simpler to use
Typically does not support multi-user access
Less expensive
Limited to smaller databases
Fits the needs of many small businesses and Limited functionality (i.e. no support for
home users
complicated transactions, recovery, etc.)
Popular FMSs are packaged along with the
operating systems of personal computers (i.e. Decentralization of data
Microsoft Cardfile and Microsoft Works)
Good for database solutions for hand held
Redundancy and Integrity issues
devices such as Palm Pilot
Typically, File Management Systems provide the following advantages and disadvantages:
The goals of a File Management System can be summarized as follows (Calleri, 2001):

Data Management.
application.

Generality with respect to storage devices. The FMS data abstractions and access
methods should remain unchanged irrespective of the devices involved in data
storage.

Validity. An FMS should guarantee that at any given moment the stored data reflect
the operations performed on them.

Protection. Illegal or potentially dangerous operations on the data should be

controlled by the FMS.

Concurrency. In multiprogramming systems, concurrent access to the data should be

allowed with minimal differences.

An FMS should provide data management services to the

Performance.
functionality.

Compromise

data

access

speed

and

data

transfer

rate

with

From the point of view of an end user (or application) an FMS typically provides the
following functionalities (Calleri, 2001):

File creation, modification and deletion.

Ownership of files and access control on the basis of ownership permissions.

Facilities to structure data within files (predefined record formats, etc).

Facilities for maintaining data redundancies against technical failure (back-ups, disk
mirroring, etc.).

Logical identification and structuring of the data, via file names and hierarchical
directory structures.

Database Management Systems

Database Management Systems provide the following advantages and disadvantages:
Advantages
Greater flexibility

Disadvantages
Difficult to learn
Packaged separately from the operating
system (i.e. Oracle, Microsoft Access,
Lotus/IBM Approach, Borland Paradox, Claris
FileMaker Pro)
Slower processing speeds

Good for larger databases

Greater processing power

Fits the needs of many medium to large-sized
Requires skilled administrators
organizations
Storage for all relevant data
Expensive
Provides user views relevant to tasks
performed
Ensures
data
integrity
by
transactions
(ACID
test
=
consistency, isolation, durability)

managing
atomicity,

Supports simultaneous access

Enforces design criteria in relation to data
format and structure
Provides backup and recovery controls
Advanced security
The goals of a Database Management System can be summarized as follows :

Data storage, retrieval,

implementation details)

A user-accessible catalog

Transaction support

Concurrency control services (multi-user update functionality)

Recovery services (damaged database must be returned to a consistent state)

Authorization services (security)

and

update

(while

hiding

the

internal

physical

Support for data communication Integrity services (i.e. constraints)

Services to promote data independence

Utility services (i.e. importing, monitoring, performance, record deletion, etc.)

The components to facilitate the goals of a DBMS may include the following:

Query processor

Data Manipulation Language preprocessor

Database manager (software components to include authorization control, command

processor, integrity checker, query optimizer, transaction manager, scheduler,
recovery manager, and buffer manager)

Data Definition Language compiler

File manager

Catalog manager

Database Management System Vs File Management System

1. A database management system coordinates both the physical and the logical access to
the data, whereas a file-processing system coordinates only the physical access.
2. A database management system reduces the amount of data duplication by ensuring that
a physical piece of data is available to all programs authorized to have access to it, whereas
data written by one program in a file-processing system may not be readable by another
program.
3. A database management system is designed to allow flexible access to data (i.e.,
queries), whereas a file-processing system is designed to allow predetermined access to
data (i.e., compiled programs).
4. A database management system is designed to coordinate multiple users accessing the
same data at the same time. A file-processing system is usually designed to allow one or
more programs to access different data files at the same time. In a file-processing system,
a file can be accessed by two programs concurrently only if both programs have read-only
access to the file.
5. Redundancy is control in DBMS, but not in file system
6. Unauthorized access is restricted in DBMS but not in file system.
7. DBMS provide backup and recovery. When data is lost in file system then it not recover.
8. DBMS provide multiple user interfaces. Data is isolated in file system,
9. A database is generally used for storing related, structured data, with well defined data
formats, in an efficient manner for insert, update and/or retrieval (depending on
application).

On the other hand, a file system is a more unstructured data store for storing arbitrary,
probably unrelated data. The file system is more general, and databases are built on top of
the
general
data
storage
services
provided
by
file
systems.
10. There are also differences in the expected level of service provided by file systems and
databases. While databases must be self consistent at any instant in time (think about
banks tracking money!), provide isolated transactions and durable writes, a file system
provides much looser guarantees about consistency, isolation and durability. The database
uses sophisticated algorithms and protocols to implement reliable storage on top of
potentially unreliable file systems. It is these algorithms that make database storage more
expensive in terms of processing and storage costs that make general file systems an
attractive option for data that does not require the extra guarantees provided by a
database.
11. As technology moves forward, though, the lines are blurring, as some file systems pick
up features previously the domain of databases (transactions, advanced queries) and some
databases relax the traditional constraints of consistency, isolation and durability. ZFS and
BTRFS might be considered examples of the former, MongoDB and CouchDB examples of
the latter.

Roles of DBA
A database administrator's responsibilities can include the following tasks:
A database administrator (DBA) directs or performs all activities related to maintaining a
successful database environment. Responsibilities include designing, implementing, and
maintaining the database system; establishing policies and procedures pertaining to the
management, security, maintenance, and use of the database management system; and
training employees in database management and use. A DBA is expected to stay abreast of
emerging technologies and new design approaches. Typically, a DBA has either a degree in
Computer Science and some on-the-job training with a particular database product or more
extensive experience with a range of database products. A DBA is usually expected to have
experience with one or more of the major database management products, such as
Structured Query Language, SAP, and Oracle-based database management software.

Installing and upgrading the database server and application tools ,

Allocating system storage and planning future storage requirements for the database
system

Modifying the database structure, as necessary, from information given by

application developers

Enrolling users and maintaining system security

Ensuring compliance with database vendor license agreement

Controlling and monitoring user access to the database

Monitoring and optimizing the performance of the database

Planning for backup and recovery of database information

Maintaining archived data

Backing up and restoring databases

Contacting database vendor for technical support

Generating various reports by querying from database as per need

Installation, configuration and upgrading of Microsoft SQL Server/ Evaluate

MSSQL/MySQL/Oracle features and MSSQL/MySQL/Oracle related products.
Establish and maintain sound backup and recovery policies and procedures.
Take care of the Database design and implementation.
Implement and maintain database security (create and maintain users and roles,
assign privileges).
Database tuning and performance monitoring.
Application tuning and performance monitoring.
Setup and maintain documentation and standards.
Plan growth and changes (capacity planning).
Work as part of a team and provide 724 supports when required.
Do general technical trouble shooting and give consultation to development teams.
Interface with MSSQL/MySQL/Oracle for technical support. ITIL Skill set
requirement (Problem Management/Incident Management/Chain Management etc)

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 as a way
to unify the network and relational database views. Simply stated, the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram, which is used to visually
represent data objects. For the database designer, the utility of the ER model is:
It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
It is simple and easy to understand with a minimum of training. Therefore, the model can
be used by the database designer to communicate the design to the end user.
In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

Advantages and Disadvantages of E-R Data Model

Following are advantages of an E-R Model:
Straightforward relation representation: Having designed an E-R diagram for a
database application, the relational representation of the database model becomes relatively
straightforward.
Easy conversion for E-R to other data model: Conversion from E-R diagram to a
network or hierarchical data model can easily be accomplished.

 Graphical representation for better understanding: An E-R model gives graphical and
diagrammatical representation of various entities, its attributes and relationships between
entities. This is turn helps in the clear understanding of the data structure and in minimizing
redundancy and other problems.
Disadvantages of E-R Data Model
Following are disadvantages of an E-R Model:
No industry standard for notation: There is no industry standard notation for
developing an E-R diagram.
Popular for high-level design: The E-R data model is especially popular for high level.
Advantages

Disadvantages

Conceptual simplicity

Limited constraint representation

Visual representation

Limited relationship representation

Effective communication

No representation of data
manipulation

Integration with the relational database

model

Loss of information

Advantages of ER Model
1. Conceptually it is very simple Making the ER Diagram is a very easy
process. You just know about the notations about various types of entities,
their attributes and the relationships between these entities.
2. Better visual representation The E-R model gives graphical and
diagrammatical representation of various entities, their attributes and
relationships between entities. So, It helps in the clear understanding of the
data structure and in minimizing redundancy and other problems.
3. Effective Communication Tool It is an effective communication tool
among users, domain experts ans database designers.
4. It is highly integrated with relational model, so converting ER Diagrams
to tables is very simple.
5. Easy conversion to any Data Model Conversion of ER Diagram to any
other data model like network model, hierarchical model and the relational
model is very easy.
Disadvantages of ER Model
1. Limited Constraints and Specifications Example : minimum Cardinality
2. Loss of Information Content Example FAN Trap, CHASM Trap (may
be)
3. Limited Relationship Representation (only Binary Relationship)
4. No industry standard for notation i.e. there is no industry standard
notation for developing an E-R diagram.
5. Popular for high-level design The E-R data model is especially popular
for high level design.

6. No representation of data manipulation