You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2006/04/01 03:02:58 UTC

[Db-derby Wiki] Update of "StmtExecutionPlan" by BryanPendleton

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by BryanPendleton:
http://wiki.apache.org/db-derby/StmtExecutionPlan

The comment on the change is:
Nice page! I corrected a minor typo, and added some sub-headings to the page

------------------------------------------------------------------------------
  = Interpreting Some Information in the Statement Execution Plan =
+ 
+ == Enabling the display of the execution plan ==
  
  The RUNTIMESTATISTICS attribute can be used to obtain information about the length
  of the compile time and the execution time for each statement executed within
@@ -8, +10 @@

  sometimes referred to as the Query Plan.
  
  An overview for using RUNTIMESTATISTICS is available in the Derby documentation
+ in [http://db.apache.org/derby/docs/dev/tuning/ctundepth13055.html the Tuning Guide], 
- in the Tunning Guide, under the Section "Working with Run``Time``Statistics".
+ under the Section "Working with Run``Time``Statistics".
  
- Intrepreting the information in the Statment execution plan depends on various
+ Interpreting the information in the Statment execution plan depends on various
  factors including the isolation level of the transaction, the type of result set
  and the type of statement (insert, update, delete or select.)
+ 
+ == Reading lock information from the execution plan ==
  
  Looking at the truncated output from the statement execution plan below one might 
  ask how many rows were locked and how many rows are currently locked?