I

ACKNOWLEGMENT-


I am using this opportunity to express my gratitude to everyone who
supported me in completing my assignment within the given time by our
lecturer. I am thankful for their aspiring guidance, invaluably constructive
criticism and friendly advice during the practical work. I am sincerely
grateful to them for sharing their truthful and illuminating vies on a
number of issues related to the assignment.
I express my warm thanks to Dr. KUMAR SHANTANU and Dr. VINAY for
their support and guidance.
Thank you,
Manisha goswami
12/4278

II

CONTENT-
INTRODUCTION III
DATA MANAGEMENT 1
DATA LIFE CYCLE 2
-Data creation and Acquisition 3.....
-Use 4.
-Data Modification 4.
-Archiving 5
-Repurposing 8
-Disposal 8.
-Managing the life cycle 9.
-DATABASE TECHNOLOGY 9.
-DATABASE ARCHITECTURE 11
-DATABASE MANAGEMENT SYSTEMS 14
-INTERFACES 19
-IMPLEMENTATION 20
-INFRASTRUCTURE 22
-SUMMARY 23



III

INTRODUCTION
DATABSES, which provide the long-term memory of computer operations, take on a variety of names,
depending on their structure, contents, use, and amount of data they contain. Two technologies often
confused with databases are disk servers and file servers. A disk server is a node in a local area network
that acts as a remote disk drive. A disk server can be divided into multiple volumes, some of which are
shared by all users on the server, and others of which can be accessed only by a specific user, as defined
by username and password login. At the next level in sophistication is the file server, which can be
thought of as a disk server with intelligence. A file server not only stores files but manages the network
requests for them and maintains order as users request and modify files. At the simplest level of a true
database is the data repository, a database used as an information storage facility, with minimal analysis
or querying functionality. A data repository is a structured, systematically collected storehouse of data
distilled or mirrored from a single application, such as sequencing machines, or clinical system. Next up
the hierarchy of complexity and capability is the data mart, a searchable database system, organized
according to users likely needs. Data mart contains a subset of data contained in other databases as
opposed to an indiscriminate mass copying of all the data from another database. One step up from the
data mart is the data warehouse, a central database, frequently very large, that can provide
authenticated researchers with access to all of an institutions information. That is, a data warehouse is
usually populated with data from a variety of non-compatible sources, such as sequencing machines,
clinical systems, or national genomic database. Because a data warehouse combines data from a variety
of application-oriented databases into single system, data from disparate sources must be cleaned,
encoded, and translated so that a standard set of analytical tools can be used with the data.
The data warehouse is distinguished from application-specific databases in the way the data destined for
incorporation in a data warehouse are selected, prepared, and loaded, and how the underlying database
is optimized for use. Once data to be included in the data warehouse have been identified, the data are
cleaned, merged, and the original database structures are manipulated to mirror those of the data
warehouse.
Its important to note that when the specialized vocabulary is peeled away, data repositories, data marts,
and data warehouse are simply databases. The three architectures share the usual issues of database
design, provision for maintenance, security, and periodic modification. Similarly, data repositories, data
marts, and data warehouse are built with some form of a database management system, a program that
allows researchers to store, process and manage data in a systematic way.




IV

Figure 1. Database Nomenclature. Data
repositories, data marts, and data
Warehouses differ primarily in the diversity
of data sources that contribute to their
contents.