X hits on this document

Word document

SAP with Microsoft SQL Server 2005: Best Practices for High Availability, Maximum Performance, and ... - page 34 / 76





34 / 76

SAP with Microsoft SQL Server 2005: Best Practices for High Availability, Maximum Performance, and Scalability30

Installation and Configuration

The cornerstone of a successful SAP with SQL Server 2005 installation is careful planning. For example, no installation should begin before all prerequisite tasks are finished. Prerequisite tasks include defining the machine names, developing the physical layout of the SAP product database, and sizing the disk space requirements. The number of data files depends on the configuration and must be defined in advance because this is difficult to change after the SAP system is in production.

SQL Server installation with SAP

The installation of SAP products does not require that SQL Server 2005 be configured in a special way, with the exception of the code page. For more information, see Collation and Code Page in the preceding section.

Before SAP starts the data import, it automatically changes a few SQL Server configuration parameters, such as the network packet size, to guarantee optimum performance during the initial import of SAP data.

During the initial data load, the SAP database is set to the simple recovery model. Most of those settings are reversed when the data load and the installation of the SAP product are complete.

Volume and growth projections

Projections for the volume and growth of SAP product databases over time are often underestimated. The growth rate is typically higher than expected. When growth projections are in error, SAP products can require reconfiguration and adaptation on the hardware or on the database to satisfy hardware growth requirements.

Note that any sizing of an SAP system must be done by a SAP-certified hardware partner.

For the initial configuration, ensure that the size of the database is sufficient to sustain the first 6 to 12 months of production. In addition, assume that each subsequent release of a SAP product will tend to increase the weekly or monthly growth rate, as compared to its predecessor. For example:

For midrange companies, the mySAP or SAP BW database can grow from 2 to 5 GB each week.

For larger companies, the database can grow from 10 to 12 GB each week.

For very large implementations, the database can grow from 20 to 30 GB each month.

Do not use SQL Server 2005 features to shrink the database or data file. Archiving data from a SAP database using SQL Server 2005 shrink functionality causes opposite logical-to-physical page order within one extent (a 64-KB block of 8 pages). This could be problematic for the Storage Area Network back-end read-ahead functionality.

Microsoft Corporation © 2005

Document info
Document views323
Page views323
Page last viewedWed Jan 18 06:28:46 UTC 2017