![Database name length restriction [CR #365281]](arrow-left.gif){kind=icon}
![Dbspace naming in RESTORE command [CR #561366]](arrow-right.gif){kind=icon}
When you allocate file system files for dbspaces (System, IQ Main, or IQ Temporary), do not place the files on a file system that is shared over a local area network. Doing so can lead to poor I/O performance and other problems, including overloading the local area network. On UNIX and Linux platforms, avoid Network File System (NFS) mounted file systems. On Windows, do not place dbspace files on network drives owned by another server. These file placement recommendations also apply to log files.
To avoid conflicts, Sybase recommends that dbspace management be performed by a single database administrator on a single connection.
Performance related to randomly accessed files, including the System, IQ Main, and IQ Temporary dbfiles, can be improved by increasing the number of disk drives devoted to those files. Performance related to sequentially accessed files, including the transaction log and message log files, can be improved by locating these files on dedicated disk drives.
Suggestions to reduce file placement impact on performance:
Keep random disk I/O away from sequential disk I/O.
Place the database file, temporary dbspace, and transaction log file on the same physical machine as the database server.
Isolate Sybase IQ database I/O from I/O for proxy tables in other databases, such as Adaptive Server Enterprise.
Place the transaction log and message log on separate disks from the IQ store, catalog store, and temporary store, and from any proxy databases such Adaptive Server Enterprise.
