Skip to end of metadata
Go to start of metadata

Use

Number of physical writes of temporary pages: <count>


Explanation

When temporary data pages are generated to build (buffer) result sets (in JOINS or ORDER BY statements, for example), the data cache is not large enough to accommodate the temporary pages, which have to be moved into the data area. However, these pages must be exported out of the data area again for the further processing of the SQL statement.


User Response

Find the statement that causes these large (buffer) result sets to be created, and check the access strategies for this statement.

Note:

For information on creating optimized SQL statements, see the SQL Optimizer documentation.

 

More Information

Relevant  DB-Analyzer Files
Helpful with ...
DBAN_CACHES.csv Successful and unsuccessful accesses to caches, and also hit rates 
DBAN_IO.csv Read and write operations to cache pages and data pages
DBAN_IOTHREADS.csv Number and duration of physical write and read operations (I/O threads)
SAP Note
Helpful with ...
  
Expert Sessions (Link to trainings)
Content / Helpful with ...
Session 16: SAP MaxDB SQL Query Optimization (Part 1)
Session 16: SAP MaxDB SQL Query Optimization (Part 2)
Find detailed information about different optimizer strategies and performance optimization.
Session 26: SAP MaxDB I/O Concept  
Documentation (links)
Helpful with ...
SQL Optimizer 
  • No labels