oracle_sql_processing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
oracle_sql_processing [2019/08/11 20:58] – [SQL Processing] andonovjoracle_sql_processing [2020/10/19 07:29] (current) 86.49.253.137
Line 1: Line 1:
 =====Overview===== =====Overview=====
-The SQL processing like any other processing of code. It comes from a human and needs to go back to a human :) The problem is, through how many stops it will pass.+The SQL processing like any other processing of code. It comes from a human and needs to go back to a human :) The problem is, through how many stops it will pass
 Below you can see a basic representation on the possible wait times for any query: Below you can see a basic representation on the possible wait times for any query:
  
Line 6: Line 6:
  
 This picture, clearly displays why it isn't ALWAYS A DATABASE FAULT :) Often the database is intermediary point between the User and the data.  This picture, clearly displays why it isn't ALWAYS A DATABASE FAULT :) Often the database is intermediary point between the User and the data. 
 +
 +=====Calls=====
 +Before we start speaking of SQL processing, we should discuss something very important and that is how ORACLE communicate and operate in general.
 +Oracle kernel is using requests called "calls". These "calls" represent request to certain structures and are generally devided into two groups:
 +
 +DB Calls:
 +  * Parse
 +  * Execute
 +  * Fetch
 +
 +Operation System (OS) Calls:
 +  * WAIT
 +  * STAT
 +
 +These calls are accomplished using different functions:
 +
 +{{ :sql_process_calls.gif?600 |}}
  
 =====SQL Processing ===== =====SQL Processing =====
Line 30: Line 47:
   * Close Cursor   * Close Cursor
  
-*-Optional steps in case of hard parse+*- Only when hard parse is needed
  
  • oracle_sql_processing.1565557125.txt.gz
  • Last modified: 2019/10/18 20:04
  • (external edit)