X hits on this document

Word document

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





75 / 76

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

SAP applications on a 64-bit platform

The main problem with running SAP application instances using 32-bit computing is that the address space for a single process of the SAP instance is limited to 3 GB. Because of SAP’s extensive buffering for the NetWeaver Application Server, those buffers use a large amount of memory in the address space of a process. Over the last six years, SAP releases have nearly doubled their demand on memory.

In fact, situations where SAP users are performing processing that reaches the upper limits of the 32-bit x86 platform are becoming more frequent. In particular, the usage of SAP Unicode products increases the problem because the Unicode products address memory in a severe manner. For SAP Unicode products, the recommendation is to use a 64-bit platform to run the SAP Application Server Layer.

In addition, 64-bit computing is in demand with the SAP® Advanced Planning & Optimization (SAP APO) component of mySAP SCM. In particular, the SAP APO liveCache is an in-memory database where 64-bit addressability is mandatory.

SAP availability and support of 64-bit platforms

SAP supports the SQL Server 2005 (64-bit) 32-bit, IA64, and x64 platforms. However, in configurations that use Microsoft clustering, it might be necessary to have SAP executables running on the native platform. In this case, make sure SAP supports the 64-bit computing platform for the specific SAP product and release that is in use. More recent SAP products are available on IA64. For x64, the SAP ABAP stack should become available toward the beginning of 2006 for the most recent SAP releases.

Microsoft Corporation © 2005

Document info
Document views307
Page views307
Page last viewedMon Jan 16 16:22:51 UTC 2017