Solution : https://service.sap.com/sap/support/notes/766349 (Connexion à SAP Service Marketplace requise)
Résumé :
La note SAP discute de l'importance cruciale de l'optimisation SQL, détaillant les méthodes pour identifier, évaluer et améliorer les instructions SQL qui consomment beaucoup de ressources pour améliorer la performance du système. Elle détaille l'identification des instructions provoquant de grandes demandes en I/O et CPU à travers des outils d'analyse comme la Transaction ST04 de SAP et d'autres services de surveillance. Elle souligne la nécessité de révisions régulières des instructions SQL pour un fonctionnement efficace du système, abordant les complications résultantes telles que les attentes actives de tampon. Les informations sur les instructions SQL exécutées sont accessibles via le Shared Cursor et peuvent être approfondies par des dossiers de transactions pour optimisation. Les techniques incluent l'ajustement des lectures de tampon, les lectures de disque, et la compréhension des comportements de curseur, ainsi que l'examen de l'alignement et des optimisations du code source ABAP, assurant une meilleure gestion des données et efficacité du système sans compromettre la sécurité.
Mots Clés :
select ltap~lgnum ltap~tanum ltap~tapos ltap~vltyp ltap~nltyp ltak~bwlvs ltak~bdatu ltak~bzeit, index rowid ltap index range scan ltap~0 sort join table access, selecting transaction st04-> detail analysis menu-> sql request, index rowid ltak index range scan ltak~, ltak~tanum = ltap~tanum, sap j2ee engine visual administrator activate, ltak~lgnum = ltap~lgnum, sap early watch alert services, single highly processing-intensive sql statement, previously barely usable system function
Notes associées :
| 1601951 | Self Service 'SQL Statement Tuning' - Prerequisites and FAQ |
| 1128663 | Oracle 10g: SQL trace using auditing |
| 1100926 | FAQ: Network performance |
| 1093107 | Costly SQL statement due to synchronous matchcodes |
| 1037755 | Performance problems with ASSM tablespaces |
| 913247 | Performance problems due to open changes |
| 912620 | FAQ: Oracle indexes |
| 896717 | Problems with tables in ASSM tablespaces |
| 881083 | Blocking factors on Oracle-based systems |
| 853576 | Oracle 10g: Performance analysis w/ ASH and Oracle Advisors |
| 832343 | FAQ: Clustering factor |
| 825653 | Oracle: Common misconceptions |
| 806554 | FAQ: I/O-intensive database operations |
| 797629 | FAQ: Oracle histograms |
| 793113 | FAQ: Oracle I/O configuration |
| 772497 | FAQ: Oracle Hints |
| 771929 | FAQ: Index fragmentation |
| 767414 | FAQ: Oracle latches |
| 762808 | FAQ: Keep pool |
| 756335 | Statistics in tables w/ heavily fluctuating volumes of data |
| 750631 | Approximations for cost calculation of the CBO |
| 745639 | FAQ: Oracle enqueues |
| 724545 | Adjusting the CBO statistics manually using DBMS_STATS |
| 723879 | Explain: System displays an incorrect access path |
| 712624 | High CPU consumption by Oracle |
| 706478 | Preventing Basis tables from increasing considerably |
| 651060 | FAQ: Oracle Parallel Execution |
| 619188 | FAQ: Oracle wait events |
| 618868 | FAQ: Oracle performance |
| 613872 | Oracle traces with ORADEBUG |
| 602667 | Perform a SQL Trace on an oracle utility or external program |
| 588668 | FAQ: Database statistics |
| 563359 | Performance optimization for tables with LOB columns |
| 502782 | Composite SAP Note ora-4030 |
| 354080 | Note collection for Oracle performance problems |
| 329914 | Expensive SQL statements composite note |
| 191492 | Performance: Customer developments in MM/WM |
| 187906 | Performance: Customer developments in PP and PM |
| 185530 | Performance: Customer developments in SD |
| 176754 | Problems with CBO and RBO |
| 135048 | Long runtimes statements w/ ROWNUM <= condition |
| 132861 | CBO: Statistics creation with SAPDBA or BRCONNECT |
| 131372 | CBO: Tuning of expensive SQL statements |
| 130480 | Database Hints in Open SQL for Oracle |
| 122718 | CBO: Tables with special treatment |
| 48230 | Parameters for the SELECT ... FOR ALL ENTRIES statement |
| 3807 | Error messages regarding rollback and undo segments |