Answer Posted / s.panda

Step1: At first we need to identified the high load SQLs or
top SQLs that are responsible for performance problem or in
another word the sql that consume application workload and
system resources. We can easily identify them by reviewing
past SQL execution history available in the system.

Step 2: Now generate execution plan of those high load sql
statements and verify that the execution plans produced by
the query optimizer for these statements perform reasonably.

Step 3: Implement corrective actions to generate better
execution plans for poorly performing SQL statements. While
taking corrective actions there is many considerations.

Explain the savepoint statement.

1088

---

Differences between Oracle 9i and 10g (Probably in terms of SQL and PL/SQL)?

3564

---

Are left and right joins the same?

1072

---

What does inner join mean?

1152

---

What is an implicit commit?

1048

---

what is msql? : Sql dba

984

---

What is normalisation in sql?

1049

---

Any attempt to navigate programmatically to disabled form in a call_form stack is allowed?

1092

---

What is the use of function "module procedure" in pl/sql?

1189

---

Can we join tables without foreign key?

955

---

What are the triggers associated with image items?

1034

---

What is the difference between the implicit and explicit cursors?

1042

---

Which one is faster ienumerable or iqueryable?

930

---

How do I find duplicates in a single column in sql?

1012

---

What do you mean by “trigger” in sql?

1066

---