PeopleSoft Learning

PSQuery Performance issues with Query Security Tables

We see PSQuery having bad performance due to many Query Security Join tables that the PSQuery tool adds to the PSQuery SQL for security.


We have few options to work around to easily improve the performance without much involving tunning from the DBA perspective which can time consuming.

 If security is not required for this query 

 Change the Query type to 'Process'. Process queries override the automatic row-level query security logic that is applied to all other types of queries.
   
    It will be useful for the PSQuery in Pagelet specific to the logged-in users where security is not important.

   If you are using Campus Solution and you don't know Campus solution specific query tables, you don't need Security to join tables.

 If Security is required

  Select the Security optimization checkbox, it will eliminate duplicate security.
  if still, more than one Security join tables are added and need improvement in performance, 
  one security join should be fine usually and for other records view of the table without security join table.