Plan resource usage before you make changes to SAP ASE configuration.
In the case of disk resources, for example, after you initialize and allocate a device to SAP ASE, that device cannot be used for any other purpose (even if SAP ASE never fills the device with data). Likewise, SAP ASE automatically reserves the memory for which it is configured, and this memory cannot be used by any other application.
For recovery purposes, always place a database’s transaction log on a separate physical device from its data. See System Administration Guide: Volume 2 > Creating and Managing User Databases.
Consider mirroring devices that store mission-critical data. See System Administration Guide: Volume 2 > Mirroring Database Devices. If your operating system supports these features, consider using disk arrays and disk mirroring for SAP ASE data.
If you are working with a test SAP ASE, for convenience, you may find it easier to initialize database devices as operating system files, rather than raw devices. SAP ASE supports either raw partitions or certified file systems for its devices.
Changing configuration options can affect the way SAP ASE consumes physical resources, especially memory.