The following are the areas of concern for tuning:

- Memory Usage

- Data Storage

- Data Manipulation

- Physical Storage

- Logic Storage

- Network Traffic

Tuning Memory Usage: In Oracle 10g, we can use the Automatic Workload Repository (AWR) toolset to gather and manage statistical data but in case of Oracle 11g, we can use new initialization parameters such as MEMORY_TARGET to further control the overall memory used by Oracle. It helps us to tune the database automatically when we don’t have time to read the AWR report.

Tuning Data Manipulation: There are two ways to tune Data manipulation in Oracle one way is through Conventional Path mode and second is Direct Path mode.

Tuning Physical Storage: We need to tune the physical storage because it limits the disk in database. This can be done by: Distributing I/O, Striping and Mirroring.

We need to first login to the data base as: SQLPLUS followed by user_name/password. Then we need to execute the following query:

CREATE USER user_name IDENTIFIED BY abcd; in this query a user_name suggest the user that is created which has a password abcd which is required for login in database.

An index is a object which is used to improve performance during retrieval of records.

CREATE [UNIQUE] INDEX index_name 

ON employee[emp_id, emp_name,dept_id]

[COMPUTE STATISTICS]

The UNIQUE keyword is used when combined values of the index should be unique.

The COMPUTE STATISTICS during the creation of index optimizes the plan of execution of the SQL statement and improves performance.

The CACHE option means how many sequences will be stored in memory for access by the application objects. The performance is faster. However in case of the database is down the data is memory is lost for the sequence.

The NO CACHE option means values are not stored in memory. So there might be some performance issue. 

A sequence is a database object that is used to generate sequential number.

CREATE SEQUENCE seqname [increment] [minimum value][maximum value][start][cache][cycle]               Nextval and currval lets us get the next value and current value from the sequence.

A database trigger is procedural code that is automatically executed in response to certain events on a particular table or view in a database. The trigger is mostly used for maintaining the integrity of the information on the database.

Syntax:

CREATE OR REPLACE TRIGGER [Trigger Name] [Before / After / Instead Of]

ON [schema].[table]

<PL/SQL subprogram>

Types of PL/SQL triggers : 

> Row trigger          - The trigger fires for each ROW affected.

> Statement trigger - The trigger is fired once when the condition is matched

> Before and After trigger - The BEFORE trigger run the trigger action before the insert, update or delete statement. The AFTER trigger runs the trigger action after the insert, update or delete statement is executes.

A package is a collection of related PL/SQL objects. The package contains a body and a specification. The package specification has the declaration which is public and can be used in the PL/SQL sub programs inside the package.

The package body holds the implementation of all the PL/SQL objects declared in the specification.

Example of a PL/SQL Package.

CREATE OR REPLACE PACKAGE emp_data AS 

PROCEDURE add_employee (

      ename VARCHAR2,

      job VARCHAR2,

      mgr NUMBER,

      sal NUMBER,

      deptno NUMBER);

END emp_actions;

CREATE OR REPLACE PACKAGE BODY emp_data AS 

PROCEDURE add_employee (

       ename VARCHAR2,

       job VARCHAR2,

       mgr NUMBER,

       sal NUMBER,

       deptno NUMBER) IS

BEGIN

         INSERT INTO emp VALUES (empno_seq.NEXTVAL, ename, job, mgr, SYSDATE, comm, deptno);

END add_employee;

END emp_data;

Advantages of  PL/SQL packages :

Packages are easier for application designing, encapsulating data, additional functionality and better performance. An application has various modules which can be placed in packages and handled easier.

Named PL/SQL blocks of code which can be invoked using parameters are called PL/SQL sub programs.

Advantages of PL/SQL subprograms are

- The application makes a single call to the database to run a block of statements which improves performance against running SQL multiple times. This will reduce the number of calls between the database and the application.

- PL/SQL is secure since the code resides inside the database thus hiding internal database details from the application. The application will only make a call to the PL/SQL sub program

- PL/SQL and SQL go hand in hand so there would be no need of any translation required between PL/SQL and SQL.