Scribd
Upload
56 views12 pages

A Software Databases

A DBMS is software that manages databases. It allows users to store, modify, and extract data from a database. Common examples are Oracle, DB2, SQL Server, MySQL. A RDBMS stores data in tables and relationships between data are also stored in tables. Data modeling involves identifying entities, attributes, relationships, and keys. Normalization reduces redundancy and ensures consistency. Performance can be improved by avoiding full table scans, using indexes appropriately, optimizing queries, and tuning additional aspects like materialized views and memory usage.

Uploaded by

pankaj_kenjale
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
56 views12 pages

A Software Databases

A DBMS is software that manages databases. It allows users to store, modify, and extract data from a database. Common examples are Oracle, DB2, SQL Server, MySQL. A RDBMS stores data in tables and relationships between data are also stored in tables. Data modeling involves identifying entities, attributes, relationships, and keys. Normalization reduces redundancy and ensures consistency. Performance can be improved by avoiding full table scans, using indexes appropriately, optimizing queries, and tuning additional aspects like materialized views and memory usage.

Uploaded by

pankaj_kenjale
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 12

DBMS

• Database Management System (DBMS) is


a software designed for the purpose of managing
databases.

• It’s a collection of programs that enables you to


store, modify, and extract information from a
database.

• Typical examples of DBMSs include Oracle, DB2,


Microsoft Access, Microsoft SQL Server, Postgres,
MySQL.
RDBMS
• RDBMS is a DBMS in which data is stored
in the form of tables and the relationship
among the data is also stored in the form of
tables.
Data Modeling
• Identify entity types
• Identify attributes
• Apply naming conventions
• Identify relationships
• Assign keys
• Normalize to reduce data redundancy
• Denormalize to improve performance
Normalization
• Normalization is the process of efficiently
organizing data in a database.

• There are two goals of the normalization process:


eliminating redundant data (for example, storing
the same data in more than one table) and ensuring
data dependencies make sense (only storing
related data in a table).

• Database normalization can save storage space


and ensure the consistency of data.
Rules of Data Normalization
• 1NF Eliminate Repeating Groups - Make a separate
table for each set of related attributes, and give each table a
primary key.

• 2NF Eliminate Redundant Data - If an attribute depends


on only part of a multi-valued key, remove it to a separate
table.

• 3NF Eliminate Columns Not Dependent On Key - If


attributes do not contribute to a description of the key,
remove them to a separate table.
Normalization Example
Oracle Server
• The Database – Physical files that store
data.
• The Instance – Memory structures and
background processes that are used to
access data.
SQL Statements
• Data Retrieval (SELECT)

• Data Definition Language (DDL)

• Data Manipulation Language (DML)

• Data Control Language (DCL)


PL/SQL
• Anonymous Subprograms

• Named Subprograms (Procedure, Function)


PL/SQL
»Procedure
»Function
»Packages
»Trigger
»Cursor
Performance Tuning Guidelines
• Disallow full table scans, when the WHERE clause predicates for SQL
statements process or return a very small portion of the table.

• In the where clauses, if the column data type is a number, do not use
single quotes. Likewise, if the column data type is varchar2 always use
single quotes else indexes will not be used.

• Do not use the IS NULL operator on a column that is indexed, as the


optimizer will ignore the index.

• Do not code correlated sub queries in your applications, as they consume


significant amounts of CPU resources, use inline views instead. If a join
will provide the functionality of the sub query try the join method first.

• Use NVL function wherever appropriate, as it does not require to know


the data type of column on which the function is applied.
Performance Tuning Guidelines
• Use UNION ALL in place of OR conditions in complex queries.

• Use the most selective indexes.

• Avoid Bitmap indexes on tables with heavy concurrent DML operations,


due to their inherent locking behavior.

• When doing a join of three or more tables, try to structure the query to do
the greatest elimination on the first join. Incorporating all of the restrictive
where clause conditions on one table can often do this.
• Only If the leading column of an index is referenced in the where clause
will the index be used else not.

• Keep frequently accessed lookup tables in keep memory.

• Pin frequently accessed subprograms.

You might also like