Configuration Parameters That Control SAP ASE Memory

System administrators who are configuring SAP ASE for the first time should check configuration parameters that use large amounts of SAP ASE memory, and those that are commonly changed at a large number of installations.

Review these parameters when the system configuration changes, after upgrading to a new version of SAP ASE, or when making changes to other configuration variables that use memory.

• SAP ASE Executable Code Size
  The size of executable code is not included in the value of total logical memory or max memory calculations. total logical memory reports the actual memory requirement for SAP ASE configuration, excluding any memory that is required for the executable.
• Data and Procedure Caches
  Specify the size of the data and procedure caches.
• Kernel Resource Memory
  The kernel resource memory parameter determines the amount of memory available, in 2K pages, for internal kernel purposes, such as thread pools, tasks, and monitor counters.
• User Connections
  The amount of memory required per user connection varies by platform, and changes when you change some other configuration variables, including default network packet size, stack size, stack guard size, and user log cache size.
• Open Databases, Open Indexes, and Open Objects
  The configuration parameters that control the total number of databases, indexes, partitions and objects that can be open simultaneously are managed by metadata caches, which reside in the server structures portion of memory.
• Number of Locks
  All processes in SAP ASE share a pool of lock structures.
• Database Devices and Disk I/O Structures
  The number of devices configuration parameter controls the number of database devices that can be used by SAP ASE for storing data.