Sorts of SQL Statements The rundowns in the accompanying segments give an utilitarian outline of SQL proclamations and are isolated into these classes: Information Definition Language (DDL) Statements Information Manipulation Language (DML) Statements Exchange Control Statements Session Control Statements Framework Control Statement Inserted SQL Statements Information Definition Language (DDL) Statements Information definition dialect (DDL) articulations let you to play out these errands: Make, change, and drop mapping objects Give and renounce benefits and parts Break down data on a table, file, or group Build up examining alternatives Add remarks to the information lexicon The CREATE, ALTER, and DROP orders require select access to the predefined object. For instance, an ALTER TABLE articulation comes up short if another client has an open exchange on the predefined table. The GRANT, REVOKE, ANALYZE, AUDIT, and COMMENT summons don\'t require elite access to the predetermined item. For instance, you can break down a table while different clients are redesigning the table. Prophet Database verifiably submits the present exchange previously, then after the fact each DDL explanation. Numerous DDL articulations may make Oracle Database recompile or reauthorize diagram objects. For data on how Oracle Database recompiles and reauthorizes outline objects and the conditions under which a DDL proclamation would precipitate this, see Oracle Database Concepts. DDL explanations are upheld by PL/SQL with the utilization of the DBMS_SQL bundle. See Also: PL/SQL Packages and Types Reference The DDL explanations are: Adjust ... (All announcements starting with ALTER) Examine Partner STATISTICS Review Remark Make ... (All announcements starting with CREATE) DISASSOCIATE STATISTICS DROP ... (All announcements starting with DROP) FLASHBACK ... (All announcements starting with FLASHBACK) Stipend NOAUDIT Cleanse RENAME Repudiate TRUNCATE Information Manipulation Language (DML) Statements Information control dialect (DML) explanations get to and control information in existing mapping objects. These announcements don\'t verifiably confer the present exchange. The information control dialect articulations are: CALL Erase Clarify PLAN Embed LOCK TABLE Blend SELECT Redesign The SELECT articulation is a constrained type of DML explanation in that it can just get to information in the database. It can\'t control information in the database, despite the fact that it can work on the got to information before giving back the aftereffects of the question. The CALL and EXPLAIN PLAN proclamations are upheld in PL/SQL just when executed progressively. All other DML articulations are completely bolstered in PL/SQL. Exchange Control Statements Exchange control proclamations oversee changes put forth by DML expressions. The exchange control explanations are: Submit ROLLBACK SAVEPOINT SET TRANSACTION All exchange control proclamations, aside from specific types of the COMMIT and.

1. Sorts of SQL Statements
The rundowns in the accompanying segments give an utilitarian outline of SQL proclamations
and are isolated into these classes:
Information Definition Language (DDL) Statements
Information Manipulation Language (DML) Statements
Exchange Control Statements
Session Control Statements
Framework Control Statement
Inserted SQL Statements
Information Definition Language (DDL) Statements
Information definition dialect (DDL) articulations let you to play out these errands:
Make, change, and drop mapping objects
Give and renounce benefits and parts
Break down data on a table, file, or group
Build up examining alternatives
Add remarks to the information lexicon
The CREATE, ALTER, and DROP orders require select access to the predefined object. For
instance, an ALTER TABLE articulation comes up short if another client has an open exchange
on the predefined table.
The GRANT, REVOKE, ANALYZE, AUDIT, and COMMENT summons don't require elite
access to the predetermined item. For instance, you can break down a table while different
clients are redesigning the table.
Prophet Database verifiably submits the present exchange previously, then after the fact each
DDL explanation.
Numerous DDL articulations may make Oracle Database recompile or reauthorize diagram
objects. For data on how Oracle Database recompiles and reauthorizes outline objects and the
conditions under which a DDL proclamation would precipitate this, see Oracle Database
Concepts.
DDL explanations are upheld by PL/SQL with the utilization of the DBMS_SQL bundle.
See Also:
PL/SQL Packages and Types Reference
The DDL explanations are:
Adjust ... (All announcements starting with ALTER)
Examine
Partner STATISTICS

2. Review
Remark
Make ... (All announcements starting with CREATE)
DISASSOCIATE STATISTICS
DROP ... (All announcements starting with DROP)
FLASHBACK ... (All announcements starting with FLASHBACK)
Stipend
NOAUDIT
Cleanse
RENAME
Repudiate
TRUNCATE
Information Manipulation Language (DML) Statements
Information control dialect (DML) explanations get to and control information in existing
mapping objects. These announcements don't verifiably confer the present exchange. The
information control dialect articulations are:
CALL
Erase
Clarify PLAN
Embed
LOCK TABLE
Blend
SELECT
Redesign
The SELECT articulation is a constrained type of DML explanation in that it can just get to
information in the database. It can't control information in the database, despite the fact that it
can work on the got to information before giving back the aftereffects of the question.
The CALL and EXPLAIN PLAN proclamations are upheld in PL/SQL just when executed
progressively. All other DML articulations are completely bolstered in PL/SQL.
Exchange Control Statements
Exchange control proclamations oversee changes put forth by DML expressions. The exchange
control explanations are:
Submit
ROLLBACK
SAVEPOINT
SET TRANSACTION

3. All exchange control proclamations, aside from specific types of the COMMIT and
ROLLBACK orders, are upheld in PL/SQL. For data on the limitations, see COMMIT and
ROLLBACK.
Session Control Statements
Session control proclamations progressively deal with the properties of a client session. These
announcements don't certainly submit the present exchange.
PL/SQL does not bolster session control articulations. The session control articulations are:
Change SESSION
SET ROLE
Framework Control Statement
The single framework control articulation, ALTER SYSTEM, progressively deals with the
properties of an Oracle Database example. This announcement does not certainly confer the
present exchange and is not upheld in PL/SQL.
Installed SQL Statements
Installed SQL explanations place DDL, DML, and exchange control articulations inside a
procedural dialect program. Installed SQL is upheld by the Oracle precompilers and is reported
in the accompanying books:
Pro*COBOL Programmer's Guide
Pro*C/C++ Programmer's Guide
Prophet SQL*Module for Ada Programmer's Guide
Solution
Sorts of SQL Statements
The rundowns in the accompanying segments give an utilitarian outline of SQL proclamations
and are isolated into these classes:
Information Definition Language (DDL) Statements
Information Manipulation Language (DML) Statements
Exchange Control Statements
Session Control Statements
Framework Control Statement
Inserted SQL Statements
Information Definition Language (DDL) Statements
Information definition dialect (DDL) articulations let you to play out these errands:
Make, change, and drop mapping objects
Give and renounce benefits and parts

4. Break down data on a table, file, or group
Build up examining alternatives
Add remarks to the information lexicon
The CREATE, ALTER, and DROP orders require select access to the predefined object. For
instance, an ALTER TABLE articulation comes up short if another client has an open exchange
on the predefined table.
The GRANT, REVOKE, ANALYZE, AUDIT, and COMMENT summons don't require elite
access to the predetermined item. For instance, you can break down a table while different
clients are redesigning the table.
Prophet Database verifiably submits the present exchange previously, then after the fact each
DDL explanation.
Numerous DDL articulations may make Oracle Database recompile or reauthorize diagram
objects. For data on how Oracle Database recompiles and reauthorizes outline objects and the
conditions under which a DDL proclamation would precipitate this, see Oracle Database
Concepts.
DDL explanations are upheld by PL/SQL with the utilization of the DBMS_SQL bundle.
See Also:
PL/SQL Packages and Types Reference
The DDL explanations are:
Adjust ... (All announcements starting with ALTER)
Examine
Partner STATISTICS
Review
Remark
Make ... (All announcements starting with CREATE)
DISASSOCIATE STATISTICS
DROP ... (All announcements starting with DROP)
FLASHBACK ... (All announcements starting with FLASHBACK)
Stipend
NOAUDIT
Cleanse
RENAME
Repudiate
TRUNCATE
Information Manipulation Language (DML) Statements
Information control dialect (DML) explanations get to and control information in existing

5. mapping objects. These announcements don't verifiably confer the present exchange. The
information control dialect articulations are:
CALL
Erase
Clarify PLAN
Embed
LOCK TABLE
Blend
SELECT
Redesign
The SELECT articulation is a constrained type of DML explanation in that it can just get to
information in the database. It can't control information in the database, despite the fact that it
can work on the got to information before giving back the aftereffects of the question.
The CALL and EXPLAIN PLAN proclamations are upheld in PL/SQL just when executed
progressively. All other DML articulations are completely bolstered in PL/SQL.
Exchange Control Statements
Exchange control proclamations oversee changes put forth by DML expressions. The exchange
control explanations are:
Submit
ROLLBACK
SAVEPOINT
SET TRANSACTION
All exchange control proclamations, aside from specific types of the COMMIT and
ROLLBACK orders, are upheld in PL/SQL. For data on the limitations, see COMMIT and
ROLLBACK.
Session Control Statements
Session control proclamations progressively deal with the properties of a client session. These
announcements don't certainly submit the present exchange.
PL/SQL does not bolster session control articulations. The session control articulations are:
Change SESSION
SET ROLE
Framework Control Statement
The single framework control articulation, ALTER SYSTEM, progressively deals with the
properties of an Oracle Database example. This announcement does not certainly confer the
present exchange and is not upheld in PL/SQL.
Installed SQL Statements

6. Installed SQL explanations place DDL, DML, and exchange control articulations inside a
procedural dialect program. Installed SQL is upheld by the Oracle precompilers and is reported
in the accompanying books:
Pro*COBOL Programmer's Guide
Pro*C/C++ Programmer's Guide
Prophet SQL*Module for Ada Programmer's Guide