Solution : https://service.sap.com/sap/support/notes/159316 (SAP Service marketplace login required)
Summary :
This SAP Note addresses poor performance issues with SQL Server databases from versions 7.0 upwards, often associated with fragmented database tables and indexes. It advises against reorganization as a default solution, noting that such procedures frequently fail to yield significant improvements and may introduce issues such as downtime and lock situations. The note stresses that performance issues are more likely due to other factors such as inadequate I/O systems, improper access paths, and insufficient indexing. A detailed Microsoft study is referenced, offering insights into when reorganization might be beneficial, particularly highlighting differences between OLTP (such as R/3) and OLAP (such as BW) environments in their response to defragmentation.
Key words :
efficient read-ahead mechanism, wrong access paths, false join algorithms, positive effect disappears, physically located closely, aspxsap generally advises, database locks/latches, single hotspot tables, informative article based, article explains possibilities
Related Notes :
| 534036 | SAP LT: System settings for conversions |
| 489690 | CC INFO: Copying large production clients |
| 208919 | CC-INFO: Performance as of Release 4.6 |
| 67205 | CC-INFO: Copying large and productive clients |
| 40904 | Performance during availability check |