[go: up one dir, main page]
Scribd
Upload
265 views4 pages

Database Design 1

Database design is the process of producing logical and physical models of a database system to meet user requirements. The logical model focuses on data requirements independently of physical storage, while the physical model translates the logical design onto physical storage systems using a database management system (DBMS). Popular database models include the hierarchical, network, and relational models. The design process involves determining the database purpose, identifying required information items, dividing items into tables, specifying columns and primary keys, defining relationships between tables, refining the design, and applying normalization rules.

Uploaded by

dewmini pradeepika
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
265 views4 pages

Database Design 1

Database design is the process of producing logical and physical models of a database system to meet user requirements. The logical model focuses on data requirements independently of physical storage, while the physical model translates the logical design onto physical storage systems using a database management system (DBMS). Popular database models include the hierarchical, network, and relational models. The design process involves determining the database purpose, identifying required information items, dividing items into tables, specifying columns and primary keys, defining relationships between tables, refining the design, and applying normalization rules.

Uploaded by

dewmini pradeepika
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Database Design

A database is an organized collection of data, generally stored and accessed electronically from a
computer system. Where databases are more complex they are often developed using formal design and
modeling techniques.

What is Database Design?

Database Design is a collection of processes that facilitate the designing, development, implementation
and maintenance of enterprise data management systems.

It helps produce database systems

1. That meet the requirements of the users (functional requirements)


2. Have high performance (non functional requirements)

The main objectives of database designing are to produce logical and physical designs models of the
proposed database system.

The logical model concentrates on the data requirements and the data to be stored independent of
physical considerations. It does not concern itself with how the data will be stored or where it will be
stored physically.

The physical model involves translating the logical design of the database onto physical media using
hardware resources and software systems such as database management systems (DBMS).

Database Management System (DBMS)

It is a software system that enables users to define, create, maintain and control access to the database.

A DBMS should provide;

 Data storage, retrieval and update


 User accessible catalog or data dictionary describing the metadata
 Support for transactions and concurrency
 Facilities for recovering the database should it become damaged
 Support for authorization of access and update of data
 Access support from remote locations

Database Models

A database model is a type of data model that determines the logical structure of a database and
fundamentally determines in which manner data can be stored, organized and manipulated. The most
popular example of a database model is the relational model, which uses a table-based format.

Hierarchical model

These models were popular in the 1960s, 1970s, but nowadays can be found primarily in old legacy
systems.

In a hierarchical model, data is organized into a tree-like structure, implying a single parent for each
record. A sort field keeps sibling records in a particular order. Hierarchical structures were widely used in
the early mainframe database management systems.

This structure allows one one-to-many relationship between two types of data.
Network model

The network model expands upon the hierarchical structure, allowing many-to-many relationships in a
tree-like structure that allows multiple parents.

The network model organizes data using two fundamental concepts, called records and sets. Records
contain “fields” and “sets” (not to be confused with mathematical sets) define one-to-many relationships
between records. (Eg: one owner, many members). A record may be an owner in any number of sets,
and a member in any number of sets.

Relational model

The relational model was introduced by E.F. Codd in 1970 as a way to make database management
systems more independent of any particular application. It is a mathematical model defined in terms
of predicate logic and set theory, and implementations of it have been used by mainframe, midrange and
microcomputer systems.
Design Process of the Database
1. Determine the purpose of the database - This helps prepare for the remaining steps.
2. Find and organize the information required - Gather all of the types of information to record in
the database, such as product name and order number.
3. Divide the information into tables - Divide information items into major entities or subjects,
such as Products or Orders. Each subject then becomes a table.
4. Turn information items into columns - Decide what information needs to be stored in each
table. Each item becomes a field, and is displayed as a column in the table. For example, an
Employees table might include fields such as Last Name and Hire Date.
5. Specify primary keys - Choose each table's primary key. The primary key is a column, or a set
of columns, that is used to uniquely identify each row. An example might be Product ID or Order
ID.
6. Set up the table relationships - Look at each table and decide how the data in one table is
related to the data in other tables. Add fields to tables or create new tables to clarify the
relationships, as necessary.
7. Refine the design - Analyze the design for errors. Create tables and add a few records of
sample data. Check if results come from the tables as expected. Make adjustments to the
design, as needed.
8. Apply the normalization rules - Apply the data normalization rules to see if tables are structured
correctly. Make adjustments to the tables, as needed.

You might also like