solidDB Help : Configuring and administering : Administering solidDB : Creating a new database : Setting up database environment
  
Setting up database environment
By default, the solidDB database files, log, message, and trace files are created in the solidDB working directory. For production environments, you might want to set up an environment where, for example, database files, backup files, and log files are located on different disks.
Default working directory settings
A working directory is the directory that contains the files that are associated with running a particular solidDB instance. The working directory can be defined by using the SOLIDDIR environmental variable.
The following table shows the most common solidDB files, their factory value locations, and how to modify the locations.
 
File
Factory value location
How to modify
license file (solid.lic or solideval.lic)
working directory
Location cannot be changed. License files are always in the working directory.
solid.ini configuration file
working directory
Location cannot be changed. solid.ini configuration file is always in the working directory.
database files (solid.db)
working directory
Define with IndexFile.FileSpec parameter
transaction log files (sol#####.log)
working directory
Define location with Logging.LogDir parameter
or
Define location and file name with Logging.FileNameTemplate parameter.
Note If you specify a directory for the log files, the directory must exist before you start solidDB: solidDB cannot create directories.
message file (solmsg.out)
working directory
Location and name cannot be changed; the solmsg.out file is always output in the working directory.
error file (solerror.out)
working directory
Location and name cannot be changed; the solerror.out file is always output in the working directory.
trace file (soltrace.out)
working directory
Define with Com.TraceFile parameter.
Recommendations for production environments
▪ If you do not want to run the installer on your production environment server, install solidDB on a separate server and copy the executable programs, libraries, and drivers manually to your production server, as applicable for your setup.
▪ To prevent loss of data after a disk failure, store the database files and transaction log files on different physical drives. Using different physical drives also provides better performance, especially during database checkpoints when both database files and transaction log files are written at the same time.
▪ Use local disks (instead of network disks) for storing the database files and log files.
Using local disks is especially important with a solidDB HotStandby setup. Ideally, a HotStandby configuration has the primary and secondary databases in separate nodes, each using local disks. Network disks can be a logical/physical single point of failure in the system.
Go up to
Creating a new database