It is extremely important that you understand and plan resource usage in advance. In the case of disk resources, for example, after you initialize and allocate a device to Adaptive Server, that device cannot be used for any other purpose (even if Adaptive Server never fills the device with data). Likewise, Adaptive Server automatically reserves the memory for which it is configured, and this memory cannot be used by any other application.
When planning resource usage:
For recovery purposes, always place a database’s transaction log on a separate physical device from its data. See Chapter 6, “Creating and Managing User Databases,” in System Administration Guide: Volume 2.
Consider mirroring devices that store mission-critical data. See Chapter 2, “Mirroring Database Devices,” in System Administration Guide: Volume 2. If your operating system supports these features, consider using disk arrays and disk mirroring for Adaptive Server data.
If you are working with a test Adaptive Server, for convenience, you may find it easier to initialize database devices as operating system files, rather than raw devices. Adaptive Server supports either raw partitions or certified file systems for its devices.
Changing configuration options can affect the way Adaptive Server consumes physical resources, especially memory. See Chapter 5, “Setting Configuration Parameters,” for details about the amount of memory used by individual parameters.
