SAP Knowledge Base Article - Preview

2748461 - ORDER BY query on the primary key is slow - SAP ASE for Business Suite


  • An ORDER BY query with SARG predicates, where the ORDER BY clause references the columns of the primary key of the table, is very slow.

SELECT * FROM TAB WHERE pk_col1 = '001' AND pk_col2 > '00000000000000608849' AND mycol = 'X' ORDER BY pk_col1, pk_col2, pk_col3

  • The primary key is defined on pk_col1, pk_col2, and pk_col3
  • An index exists on the primary key: TAB~0 built on pk_col1, pk_col2, and pk_col3
  • The execution plan for the running process in DBACockpit shows a table scan on TAB
  • The table scan uses the 128K large i/o pool



  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite


SAP Adaptive Server Enterprise 16.0


"ORDER BY", index, "table scan", CR816291, CR#816291, 816291, "primary key", slow , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.