several commercial systems; e.g., Adabas D, IBM UDB, Informix Adaptive Server, Microsoft SQL Server, or Oracle 8. Obviously, very good performance is crucial for users of SAP R/3. In many companies, transactions of thousands of users must be processed concurrently by SAP R/3 and the underlying database system. In addition, the size of the database can become very large. Today, the largest SAP R/3 databases have about 1.5 terabytes; in a few years, these databases are likely to grow several times that size as a result of new R/3 releases and developments; e.g., component architecture or SAP’s business information warehouse. Unfortunately, tuning the performance of an SAP R/3 system is very di cult because both the R/3 application system and the underlying database system must be tuned. Furthermore, the performance of an R/3 system can su er because parts of R/3 were designed and implemented in the early eighties at a time when commercial database systems and their interfaces were immature. Finally, SAP R/3 is an open system that allows customers and third-party vendors to integrate specialized modules which are not part of the R/3 standard. Such modules can severely hurt the performance of the whole system, if they are...
Website: www.dbis.ethz.ch | Filesize: 125kb
No of Page(s): 12
Download Performance Tuning for SAP R/3 Copyright 1997 IEEE. Personal use ....pdf
No comments:
Post a Comment