Int SQL PLSQL
Int SQL PLSQL
Using Cursor we can perform row by row processing so we can perform row wise
validation or operations on each row.
Cursors can provide the first few rows before the whole result set is assembled.
Without using cursors, the entire result set must be delivered before any rows are
displayed by the application. So using cursor, better response time is achieved.
If we make updates to our without using cursors in your application then we must
send separate SQL statements to the database server to apply the changes. This can
cause the possibility of concurrency problems if the result set has changed since it
was queried by the client. In turn, this raises the possibility of lost updates. So using
cursor, better concurrency Control can be achieved.
Cursors can be faster than a while loop but at the cost of more overhead.
Advantages of trigger:
2) By using triggers, business rules and transactions are easy to store in database and can be used
consistently even if there are future updates to the database.
4) When a change happens in a database a trigger can adjust the change to the entire database.
Disadvantages of trigger:
1) It is easy to view table relationships , constraints, indexes, stored procedure in database but
triggers are difficult to view.
2) Triggers execute invisible to client-application application. They are not visible or can be
traced in debugging code.
3) It is hard to follow their logic as it they can be fired before or after the database insert/update
happens.
4) It is easy to forget about triggers and if there is no documentation it will be difficult to figure
out for new developers for their existence.
5) Triggers run every time when the database fields are updated and it is overhead on system. It
makes system run slower.
A package is a group of PL/SQL types, objects, and stored procedures and functions. The
specification part of a package declares the public types, variables, constants, and subprograms
that are visible outside the immediate scope of the package. The body of a package defines the
objects declared in the specification, as well as private objects that are not visible to applications
outside the package.
Advantages:
Disadvantages:
More memory may be required on the Oracle database server when using Oracle PL/SQL
packages as the whole package is loaded into memory as soon as any object in the package is
accessed.
Updating one of the functions/procedures will invalid other objects which use different
function/procedures since whole package need to be compiled.
Predefined Exceptions
Oracle has predefined some common exception. These exceptions have a unique exception name
and error number. These exceptions are already defined in the 'STANDARD' package in Oracle.
In code, we can directly use these predefined exception name to handle them.
Error
Exception Exception Reason
Code
ORA-
ACCESS_INTO_NULL Assign a value to the attributes of uninitialized objects
06530
ORA-
CURSOR_ALREADY_OPEN Trying to open a cursor which is already opened
06511
ORA-
INVALID_CURSOR Illegal cursor operations like closing an unopened cursor
01001
ORA- When cursor variable data type is incompatible with the actual
ROW_MISMATCH
06504 cursor return type
ORA- Referring collection by an index number that is larger than the
SUBSCRIPT_BEYOND_COUNT
06533 collection size
ORA- When a 'SELECT' statement with INTO clause returns more than
TOO_MANY_ROWS
01422 one row
ORA-
ZERO_DIVIDE Dividing a number by '0'
01476
If you are new to databases, or perhaps new to Oracle, you may find the discussion on indexes
and indexing strategy complicated. Don't fret. To get started it's fairly straightforward, and as
long as you pay attention to the options relevant to day-to-day dba needs, it should remain fairly
simple.
b-tree index
The most common index type is the b-tree index. It is named b-tree after a computer science
construct of the same name. Whenever you issue the basic CREATE INDEX statement without
further modifications, you're creating a b-tree index. Without going into a lot of depth about b-
trees which you can investigate on your own, basically these store the values of the column you
have created the index on, and pointers to the actual table data to find the row itself. Keep in
mind that also means multiple lookups, one for various nodes and the leaf node of the index, and
then the table row itself. That's why Oracle's optimizer will choose in certain circumstances to
do full table scans rather than index lookup, because it may actually be faster. Also note that if
your index is on more than one column, the leading column is very important. For example if
you have a multi-column (called concatenated) index on columns c and d in that order, you can
also do a query on column c alone and use that index. In some other cases using Oracle's skip-
scan technology, one can do a query on non-leading columns as well. Do a google search on
"skip scan index access" for details.
function-based index
We mentioned that Oracle would choose not to use an index sometimes, if you're reading a lot of
rows, or your index is not selective, or you're using a column other than the leading one in a
concatenated index. What about if you want to do a case-insensitive search? Something like:
This won't use an index on first_name. Why? Because Oracle would have to go and apply the
UPPER function on ALL values in the index, so it might as well do the full table scan. This was
such a common need that Oracle created the function-based index for this purpose.
You also may see these indexes, or want to use them from time to time. Consider a column,
which includes names like "restaurant A", "restaurant B", "restaurant C" and so on. Perhaps a
not very glamorous example, but the point is a column with many unique values but not much
variation at the front. Using a reverse-key index would be ideal here, because Oracle will simple
REVERSE the string before throwing it into the b-tree. So, the result will be a more balanced,
useful, and ultimately fast index.
More Exotic Index Types on Offer
Oracle offers quite a few more sophisticated types of indexes as well. Please note, these should
be used after you've fully read the docs as they fill very specific niches.
bitmap indexes
Have a column, which is not very selective, such as gender? You might consider using a bitmap
index on it. That's what they were created for. But also consider what's happening behind the
scenes. Generally bitmap indexes become useful when you have a whole bunch of them on
different columns so that they can all be used together to be more selective on rows that
otherwise you'd need a full table scan for. So one, use them when you can have quite a few on
different columns. Secondly, these indexes were designed for data warehouses, so the
presumption is data that does not change much. They are not meant for transactional or high
update databases. Updates on tables with bitmap indexes are, shall we say, less than efficient.
These indexes take bitmap indexes one step further. They completely take the bitmapped
columns out of the table data, and store it in the index. The presumption is that those sets of
columns will always be queried together. Again, these are meant for data warehousing
databases. The create statement looks like a CREATE BITMAP INDEX except it has a WHERE
clause at the end!
compressed indexes
This is really an option to a normal b-tree index. It results in fewer leaf nodes, so less overall I/O
and less to cache. All of this means Oracle's optimizer will be just a little more likely to use
these than a normal uncompressed index. There is a cost to all of this, in CPU to uncompress
when you access these. Also, in reading about how the optimizer uses these, and choosing the
proper compression level, it begins to look daunting. Your mileage may vary.
descending
These are a special type of function-based index. They are obviously optimized for ORDER BY
x, y, z DESC clauses.
partitioned indexes
If you have a partitioned table, a whole world of new index types opens up to you, from ones that
index across all the partitions (global) to ones that are focused on each partition individually
(local). Check the documentation for details.
cluster indexes
I personally have never seen these in the wild. All I've read is they have performance issues left
and right. Basically, you take two tables with one column in common, and that column has a
cluster index on it.
domain indexes
These indexes are used when creating custom indextypes for user defined datatypes.
invisible indexes
These are new in 11g. They are created as a normal index, but invisible to the cost based
optimizer. This can allow you to test out performance of large queries, without impacting the
live running application.
Another tool for the testers and developers. They allow you to test new indexes and their effect
on query plans, without actually building them. On gigabyte tables, the index build can be very
resource intensive, and take a lot of time. See also the Virtual Index Wizard of OEM.
miscellaneous
There are other types of indexes as well, such as Oracle TEXT for indexing CLOB or other large
text data, and Oracle Spatial. Investigation of those is left as an exercise to the reader.
Having worked extensively with MySQL, and some other databases, I can tell you it is not
Oracle's user-friendliness that makes it the world leader. I could go digress on this point, but
primarily Oracle's bread and butter is it's optimizer. This is the special sauce. And it keeps
getting better and better. There are whole books written on the topic of the Oracle's CBO (Cost
Based Optimizer) discussing hints (comments embedded in SQL to push the optimizer one way
or another), strategies for analyzing your tables and indexes, and histograms for those finicky
columns where data distribution is not balanced.
Besides keeping your statistics up to date, you'll want to always test your new queries. Use the
explain plan mechanism, and optimize to reduce overall I/O and computational sorting and
merging of data, and you will be on the path to better performance.
Conclusion
Although the Oracle landscape of index types can be intimidating, there are really only a few that
you'll use most often day-to-day. Furthermore, the optimizer has gotten so good that despite
what the naysayers may go on about; on the whole Oracle is good at getting your data
efficiently. That doesn't mean you don't need to tune your SQL, but it does mean if you keep
your statistics up to date, and ask Oracle for the minimal dataset you need, it'll probably get it for
you lickety-split!
https://www.databasejournal.com/features/oracle/article.php/3739071/Oracle-Indexing---What-
Where-When.htm
FORALL i in 1..count
UPDATE student st
FOR i in 1..count
SET st.Total =
LOOP
st.mark1+st.mark2
UPDATE student st
SET st.Total =
st.mark1+st.mark2
END LOOP
i. It works in server side programs and cannot be used in client side program
ii. You have to specify the entire row in Update's SET or Insert's Values with collections.
iii. Within a FORALL loop, you cannot refer to the same collection in both the SET clause and
the WHERE clause of an UPDATE statement. You might need to make a second copy of the collection and
refer to the new name in the WHERE clause.
iv. FORALL processes only one statement that is placed after the FORALL statement.
3. What is Bulk Collect?
It is the way of fetching rows in bulk and storing in the collection. The number of rows to be fetched is
determined by the limit variable. In the below example limit is fixed as 1000. Each time 1000 records are
fetched from cursor c1 in to c1_record and processed. The below example deletes duplicate records
using BULK COLLECT
DECLARE
limit_in integer;
CURSOR C1 is
Select min(b.rowid)
from table_name a, table_name b
where a.primary_key = b.primary_key;
C1_record C1_rec
BEGIN
limit_in:=10000 --- Can be changed based on performance
OPEN C1;
LOOP
FETCH C1 BULK COLLECT INTO C1_record LIMIT limit_in;
FORALL indx in 1..c1_record.count
DELETE FROM table_name where row_id = C1_record(i);
commit;
END LOOP;
END;
Especially when a program does a DML, use of Bulk collect and FORALL will improve the performance.
The limit is clause is optional and is placed in the FETCH statement. This determines the number of rows
to be collected. It is determined based on the size of the result fetched and the process memory
available. If result set has 1000 rows. You can make the limit to 100, t runs 10 times and process all the
1000 records.
When you set the limit higher than the memory available, out of process memory exception will be
thrown.
6. Say 100 rows are inserted in to the table using bulk collect. How to continue inserting when there are
exception in 50th record?
This can be achieved by using SAVE EXCEPTIONS. It saves the exception details, skips the record and
continue with the next.
1. Out of Process memory error is thrown out when there is no enough space to hold the collection.
2. If a collection holds 100 items, and the 50th item is deleted. Then there is a nothing in the place of 50th item. It
fails on seeing a null value in the collection.
1) %BULK_ROWCOUNT:-
%BULK_ROWCOUNT(i) stores the number of rows processed by the ith execution of an DML statement. If the ith
execution affects no rows, %BULK_ROWCOUNT(i) returns zero.
2) %BULK_EXCEPTIONS:-
It is an associative array that stores information about any exceptions encountered when using the SAVE
EXCEPTIONS clause.
SQL%BULK_EXCEPTIONS.COUNT: Represents the number of exceptions.
SQL%BULK_EXCEPTIONS(i).ERROR_CODE Specifies the Oracle error code that corresponds to the exception.
Collections are like array of elements. All elements should be of same datatypes. They are retrieved by indexes.
There are three different types.
For example:-
score Students_score
BEGIN
score('John'):=80;
score('Joe'):=90;
score('Eve'):=78;
Nested Tables:-
It is a one dimensional array. The length of the array can be extended and the elements can be deleted. If elements
are deleted, it creates a space and that position is skipped.
For Example:-
It creates a datatype which has all the columns that are in student table and in the same order.
Say the table has two columns name , id and marks
name student_name -- creating a object for the nested table
SELECT *
BULK COLLECT INTO name
FROM student
They can be accessed with continuos numbers from 1. name.count gives the number of elements in the array. The
length of the array is not prefixed. You can extend (name.extend)the array and add values. you can delete an ith item
by name.delete(i) or delete(i,j) to delete items between i and j
The nested tables can be stored in Database and Associative arrays cannot be stored in database.
VARRAYS:-
It is the fixed length array. The length of the array is declared along with the datatype it can hold.
TYPE student_name is VARRAY(14) of student%rowtype
name student_name
It is same as the nested table except the maximum size being specified. The advantage of VARRAY over nested
table is it can retrieve the elements in the same order that it has been entered.
10. INSERT ALL can be used only with collections like BULK COLLECT or FOR ALL?
It is not necessary to use INSERT ALL with collections data type , Insert ALL is used to insert records multiple
records in to same or different tables at the same time.
INSERT ALL
INTO MyTable VALUES ('a', 1, 'TRUE')
INTO MyTable VALUES ('b', 2, 'FALSE')
INTO OnTable VALUES ('Structure', 'LION', 1234)
SELECT * FROM dual;
http://easetheinterview.blogspot.com/2017/09/plsql-interview-questions-forall-and.html
https://www.techfaq360.com/viewTutorial.jsp?tutorialId=197
https://sql-plsql-database.blogspot.com/p/records.html
6.
What are % TYPE and % ROWTYPE? What are the advantages of using these over datatypes?
% TYPE provides the data type of a variable or a database column to that variable.
% ROWTYPE provides the record type that represents a entire row of a table or view or columns selected
in the cursor.
The advantages are: I. need not know about variable's data type
ii. If the database definition of a column in a table changes, the data type of a variable changes
accordingly.
7.
E.g. TYPE r_emp is RECORD (eno emp.empno% type,ename emp ename %type );
e_rec emp% ROWTYPE
Cursor c1 is select empno,deptno from emp;
e_rec c1 %ROWTYPE.
8.
Objects of type TABLE are called "PL/SQL tables", which are modelled as (but not the same as) database
tables, PL/SQL tables use a primary PL/SQL tables can have one column and a primary key.
9.
Cursor is a named private SQL area from where information can be accessed.
Cursors are required to process rows individually for queries returning multiple rows.
10.
There are two types of cursors, Implict Cursor and Explicit Cursor.
PL/SQL uses Implic
11.
What are the PL/SQL Statements used in cursor processing?
DECLARE CURSOR cursor name, OPEN cursor name, FETCH cursor name INTO <variable list> or Record
types, CLOSE cursor name.
12.
13.
Cursor for loop implicitly declares %ROWTYPE as loop index,opens a cursor, fetches rows of values from
active set into fields in the record and closes when all the records have been processed.
14.
Cursor C1 is
Select empno,
ename from emp;
Begin
open C1; loop
Fetch C1 into
eno.ename;
Exit When
C1 %notfound;-----
commit;
end loop;
end;
The cursor having query as SELECT .... FOR UPDATE gets closed after COMMIT/ROLLBACK.
The cursor having query as SELECT.... does not get closed even after COMMIT/ROLLBACK.
15.
WHERE CURRENT OF clause in an UPDATE,DELETE statement refers to the latest row fetched from a
cursor.
16.
Database trigger is stored PL/SQL program unit associated with a specific database table. Usages are
Audit data modificateions, Log events transparently, Enforce complex business rules Derive column
values automatically, Implement complex security authorizations. Maintain replicate tables.
17.
How many types of database triggers can be specified on a table? What are they?
If FOR EACH ROW clause is specified, then the trigger for each Row affected by the statement.
If WHEN clause is specified, the trigger fires according to the retruned boolean value.
18.
Is it possible to use Transaction control Statements such a ROLLBACK or COMMIT in Database Trigger?
Why?
It is not possible. As triggers are defined for each table, if you use COMMIT of ROLLBACK in a trigger, it
affects logical transaction processing.
19.
What are two virtual tables available during database trigger execution?
20.
What happens if a procedure that updates a column of table X is called in a database trigger of the same
table?
22.
Exception is the error handling part of PL/SQL block. The types are Predefined and user_defined. Some
of Predefined execptions are.
CURSOR_ALREADY_OPEN
DUP_VAL_ON_INDEX
NO_DATA_FOUND
TOO_MANY_ROWS
INVALID_CURSOR
INVALID_NUMBER
LOGON_DENIED
NOT_LOGGED_ON
PROGRAM-ERROR
STORAGE_ERROR
TIMEOUT_ON_RESOURCE
VALUE_ERROR
ZERO_DIVIDE
OTHERS.
23.
The PRAGMA EXECPTION_INIT tells the complier to associate an exception with an oracle error. To get an
error message of a specific oracle error.
24.
What is Raise_application_error?
25.
What are the return values of functions SQLCODE and SQLERRM?
SQLCODE returns the latest code of the error that has occured.
SQLERRM returns the relevant error message of the SQLCODE.
26.
27.
30.
31.
32.
IN,OUT,IN-OUT parameters.
33.
34.
BEGIN
Executable statements.
Exception.
exception handlers
end;
35.
36.
37.
The Same procedure name is repeated with parameters of different datatypes and parameters in
different positions, varying number of parameters is called overloading of procedures.
38.
39.
What are two parts of package?
The two parts of package are PACKAGE SPECIFICATION & PACKAGE BODY.
Package Specification contains declarations that are global to the packages and local to the schema.
Package Body contains actual procedures and local declaration of the procedures and cursor
declarations.
40.
What is difference between a Cursor declared in a procedure and Cursor declared in a package
specification?
A cursor declared in a package specification is global and can be accessed by other procedures or
procedures in a package.
A cursor declared in a procedure is local to the procedure that can not be accessed by other procedures.
41.
How packaged procedures and functions are called from the following ?
a. Stored procedure or anonymous block
b. an application program such a PRC *C, PRO* COBOL
c. SQL *PLUS
42.
Name the tables where characteristics of Package, procedure and functions are stored?
Part-2
What’s a PL/SQL table? Its purpose and Advantages?
A PL/SQL table is one dimensional, indexed, unbounded sparsed collection of homogeneous
Data.
PLSQL tables are used to move data into and out of the database and between client side applications and stored
sub-programs. They have attributes such as exits, prior, first, last, delete ,next . These attributes make PLSQL tables
easier to use and applications easier to maintain.
Advantages:
1 PL\SQL tables give you the ability to hold multiple values in a structure in memory so that a PL\SQL block does not
have to go to the database every time it needs to retrieve one of these values - it can retrieve it directly from the
PL\SQL table in memory.
2 Global temporary tables act as performance enhancers when compared to standard tables as they greatly reduce
the disk IO.
3 They also offer the ease-of-use of standard tables, since standard SQL can be used with them; no special array-
processing syntax is required.
What are the two basic parameters that we have to pass while registering PL/SQL procedure?
Error code and Error Buffer.
Items are imported from the legacy system using the item import interface using the SRS. How are items
imported using the UNIX /PLSQL commands with out using SRS?
1.From the operating system, use CONCSUB to submit a concurrent program. It's an easiest way to test a concurrent
program.
Normally, CONCSUB submits a concurrent request and returns control to the OS prompt/shell script without waiting
for the request to complete. The CONCSUB WAIT parameter can be used to make CONCSUB wait until the request
has completed before returning control to the OS prompt/shell script
By using the WAIT token, the utility checks the request status every 60 seconds and returns to the operating system
prompt upon completion of the request. concurrent manager does not abort, shut down, or start up until the
concurrent request completes. If your concurrent program is compatible with itself, we can check it for data integrity
and deadlocks by submitting it many times so that it runs concurrently with itself.
Syntax: CONCSUB [WAIT= [START=] [REPEAT_DAYS=] [REPEAT_END=]
To pass null parameters to CONCSUB, use '""' without spaces for each null parameter.
In words: single quote double quote double quote single quote
Following is an example of CONCSUB syntax with null parameters:
CONCSUB oe/oe OE 'Order Entry Super User' JWALSH CONCURRENT XOE XOEPACK 4 3 '""' 3
2. To Invoke a Concurrent Program using PL/SQL:
i) Just insert a row in FND_CONCURRENT_REQUESTS with the apropriate parameters and commit.
ii) Invoke the SUBMIT_REQUEST procedure in FND_REQUEST package.
FND_REQUEST.SUBMIT_REQUEST( 'AR', 'RAXMTR', '', '', FALSE, 'Autoinvoice Master Program', sc_time, FALSE,
1, 1020, 'VRP', '01-JAN-00', chr(0)
While registering a report and a pl/sql block we pass some parameters, for any pl/sql block we pass 2
additional parameters. Can u list them?
It requires two IN parameters for a PL/SQL procedure that's registered as a concurrent program in Apps. They are
1. Errcode IN VARCHAR2
2. Errbuff IN VARCHAR2
https://appsoracle-abhi.blogspot.com/2013/04/pl-sql-interview-questions-collections.html
https://www.orafaq.com/wiki/Send_mail_from_PL/SQL
Example:
BEGIN
EXECUTE IMMEDIATE 'ALTER SESSION SET smtp_out_server = ''127.0.0.1''';
UTL_MAIL.send(sender => 'me@address.com',
recipients => 'you@address.com',
subject => 'Test Mail',
message => 'Hello World',
mime_type => 'text; charset=us-ascii');
END;
/
tkyte@TKYTE816> create or replace
2 PROCEDURE send_mail (p_sender IN VARCHAR2,
3 p_recipient IN VARCHAR2,
4 p_message IN VARCHAR2)
5 as
6 l_mailhost VARCHAR2(255) := 'yourserver.acme.com';
7 l_mail_conn utl_smtp.connection;
8 BEGIN
9 l_mail_conn := utl_smtp.open_connection(l_mailhost, 25);
10 utl_smtp.helo(l_mail_conn, l_mailhost);
11 utl_smtp.mail(l_mail_conn, p_sender);
12 utl_smtp.rcpt(l_mail_conn, p_recipient);
13 utl_smtp.open_data(l_mail_conn );
14 utl_smtp.write_data(l_mail_conn, p_message);
15 utl_smtp.close_data(l_mail_conn );
16 utl_smtp.quit(l_mail_conn);
17 end;
18 /
Procedure created.
tkyte@TKYTE816> begin
2 send_mail( 'me@acme.com',
3 'you@acme.com',
4 'Hello Tom' );
5 end;
6 /
PL/SQL procedure
a. DDL triggers
b. DML triggers
There is one special type trigger called logon trigger in sql server.
DDL triggers fire in response to an event happening on the server. However, DDL
triggers do not fire in response to UPDATE, INSERT, or DELETE (DML) statements
on a table or view. Instead, they fire in response to Data Definition Language (DDL)
statements that start with the keywords CREATE, ALTER, and DROP.
Example:
CREATE TRIGGER safety
ON DATABASE
FOR DROP_TABLE, ALTER_TABLE
AS
PRINT 'You must disable Trigger "safety" to drop or
alter tables!'
ROLLBACK;
More … http://codechef4u.com/post/2015/04/15/after-trigger
More … http://codechef4u.com/post/2015/04/16/logon-trigger
12. When multiple after triggers are attached to sql table, how to control the
order of execution?
Using sp_settriggerorder procedure.
13. What is the difference between For Trigger and after trigger?
It’s same.
https://codechef4u.com/post/2016/03/04/trigger-interview-questions-and-answers
Answer :
A trigger is a special kind of a store procedure that executes in response to certain action
performed on the table like insertion, deletion or updating of data
Basically there are two logical types:
DDL triggers
DML triggers
There is one special type trigger called logon trigger in sql server.
Answer :
DDL triggers fire in response to an event happening on the server. However, DDL triggers do not
fire in response to UPDATE, INSERT, or DELETE (DML) statements on a table or view.
Instead, they fire in response to Data Definition Language (DDL) statements that start with the
keywords CREATE, ALTER, and DROP.
Answer :
DDL triggers fire in response to UPDATE, INSERT, or DELETE (DML) statements on a table or
view.
A special type of Transact-SQL stored procedure that executes one or more Transact-SQL
statements in response to a server-scoped or database-scoped event. For example, a DDL Trigger
may fire if a statement such as ALTER SERVER CONFIGURATION is executed or if a table is
deleted by using DROP TABLE.
Answer :
Instead of executing a Transact-SQL stored procedure, a CLR trigger executes one or more
methods written in managed code that are members of an assembly created in the .NET
Framework and uploaded in SQL Server.
Example:
ON DATABASE
AS
alter tables!'
ROLLBACK;
Answer :
AFTER triggers are executed after the action of the INSERT, UPDATE, MERGE, or DELETE
statement is performed successfully.
Answer :
DML trigger is executed instead of the triggering SQL statement, therefore, overriding the
actions of the triggering statements. Therefore, they can be used to perform error or value
checking on one or more columns and the perform additional actions before insert, updating or
deleting the row or rows.
Answer :
Special type of trigger fire when LOGON event of Sql Server is raised is called lo logon trigger.
You can use this trigger to audit Sql server activities, control server sessions, such as to track
login activity or limit the number of sessions for a specific login.
Answer :
Reason multiple SQL Server services are running as well as intelligence is turned on.
Answer :
Apex Tutorial
Answer :
Question 12. When Multiple After Triggers Are Attached To Sql Table, How To Control
The Order Of Execution?
Answer :
Question 13. What Is The Difference Between For Trigger And After Trigger?
Answer :
It’s same.
Answer :
Question 15. What Is The Difference Between Instead Of And After/for Trigger?
Answer :
Instead Of trigger will be fired on behalf of DML statements whereas After trigger will be fired
after DML statements.
Answer :
https://www.wisdomjobs.com/e-university/trigger-interview-questions.html
https://www.webcodeexpert.com/2013/11/what-is-cursor-advantages-and.html
https://www.scribd.com/doc/26315804/Advantage-and-Disadvantages-of-Cursor-in-Oracle
https://www.scribd.com/document/14004160/Pl-SQL-Interview-Questions
https://www.scribd.com/document/257896001/Oracle-PL-SQL-Interview-Questions
https://www.scribd.com/doc/279220171/Oracle-Pl-SQL-Interview-Questions-and-Answers-for-
Experienced
https://www.scribd.com/doc/244977462/Oracle-Pl-SQL-Interview-Questions-and-Answers-docx
http://oracle-sqlserver.over-blog.com/2015/09/what-are-the-advantage-disadvantage-of-package.html
https://www.quora.com/What-are-the-advantages-and-disadvantages-of-using-Database-Triggers
https://www.careerride.com/Oracle-disadvantages-of-trigger.aspx
https://www.developer.com/db/article.php/3379271/Oracle-Programming-with-PLSQL-Collections.htm
http://oracleappps.blogspot.com/2013/05/what-are-disadvantage-of-bulk-collection.html
http://www.oraclechennai.com/Avoiding-Collection-Exceptions.html
https://oracle-base.com/articles/9i/bulk-binds-and-record-processing-9i
https://oracle-base.com/articles/9i/bulk-binds-and-record-processing-9i