File: aguide07.htm

package info (click to toggle)
solid-desktop 2.2-3
links: PTS
area: non-free
in suites: potato, slink
size: 3,620 kB
ctags: 2,830
sloc: sh: 290; sql: 80; makefile: 64
file content (241 lines) | stat: -rw-r--r-- 17,781 bytes
parent folder | download | duplicates (2)
<HTML>
<HEAD>
<TITLE></TITLE>
<LINK REL="ToC" HREF="httoc.htm">
<LINK REL="Index" HREF="htindex.htm">
<LINK REL="Next" HREF="aguide08.htm">
<LINK REL="Previous" HREF="aguide06.htm"></HEAD>
<BODY BGCOLOR="#FFFFFF">
<P ALIGN=CENTER>
<A HREF="aguide06.htm" TARGET="_self"><IMG SRC="gaguide/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gaguide/gratop.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gaguide/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="aguide08.htm" TARGET="_self"><IMG SRC="gaguide/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>

<A NAME="E9E7"></A>
<H1>
<FONT FACE="Arial"><B>PARAMETER SETTINGS</B></FONT></H1>
<BR>
<BLOCKQUOTE>
<P>By managing the parameters<A NAME="I2"></A> of your SOLID <I>Server</I>, you can modify the environment, performance and operation of the server process. This chapter explains SOLID <I>Server</I> parameters and their settings. The topic <I>Parameter management</I> in this chapter gives you step-by-step instructions on how to view and set the parameter values on the Parameters page in SOLID <I>Remote Control</I>.
</BLOCKQUOTE>
<A NAME="E10E36"></A>
<P>
<FONT FACE="Arial"><B>Default Settings</B><A NAME="I3"></A></FONT>
<BLOCKQUOTE>
<P>When SOLID <I>Server</I> is started, it attempts to open the configuration file solid.ini first from the directory set by SOLIDDIR environment variable. If the file is not found from the path specified by this variable or if the variable is not set, an attempt is made to open the file from the current working directory. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The configuration values for the server parameters are included in this file. If the file does not exist, SOLID <I>Server</I> will use default settings for the parameters. Also, if a value for a parameter is not set in the solid.ini file, SOLID <I>Server</I> will use a default value for the parameter. The default values depend on the operating system you are using.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Generally, default settings offer good performance and operability, but in some cases modifying some parameter values can improve performance.
</BLOCKQUOTE>
<A NAME="E10E37"></A>
<P>
<FONT FACE="Arial"><B>Most Important Parameters</B></FONT>
<BLOCKQUOTE>
<P>The following paragraphs will explain the most important SOLID <I>Server</I> parameters and their default settings. See <I>Appendix B Configuration </I><I>Parameters </I>of this manual for a description of all parameters.
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I4"></A><A NAME="I5"></A><A NAME="I6"></A><A NAME="I7"></A><A NAME="I8"></A><A NAME="I9"></A><A NAME="I10"></A><A NAME="I11"></A><A NAME="I12"></A><A NAME="I13"></A><A NAME="I14"></A><A NAME="I15"></A><A NAME="I16"></A><A NAME="I17"></A><A NAME="I18"></A><A NAME="I19"></A><A NAME="I20"></A><A NAME="I21"></A><A NAME="I22"></A><A NAME="I23"></A><A NAME="I24"></A><A NAME="I25"></A><A NAME="I26"></A>[Com]
<BR></FONT>
<P>
<FONT FACE="Arial">Connect<A NAME="I27"></A>
<BR></FONT>
<P>
<FONT FACE="Arial">Listen<A NAME="I28"></A></FONT>
<BLOCKQUOTE>
<P>The parameter Connect in the [Com] section defines a network name for a client program. The client program will establish a connection to a server program with a similar Listen network name. The format for these parameters is explained in the chapter <I>Communication protocols.</I> 
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>If the connect information is defined in the client program with the SQLConnect function, this parameter is ignored. In the Windows and Windows NT operating systems the connection can be made by using SOLID <I>ODBC driver</I>. When a client program is using SOLID <I>ODBC driver</I> the ODBC Data Source Name is used and the Connect parameter has no effect. The solid.ini file, which includes the Connect parameter, must be located in the client program&#146;s working directory or in the directory set by SOLIDDIR environment variable.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The following connect line will connect a client program using the TCP/IP protocol to a SOLID <I>Server</I> running in a computer named &#145;spiff&#146; and server port number &#145;1313&#146;.
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>connect = tcpip spiff 1313</PRE></BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I29"></A><A NAME="I30"></A><A NAME="I31"></A><A NAME="I32"></A><A NAME="I33"></A><A NAME="I34"></A><A NAME="I35"></A><A NAME="I36"></A><A NAME="I37"></A><A NAME="I38"></A><A NAME="I39"></A><A NAME="I40"></A><A NAME="I41"></A><A NAME="I42"></A><A NAME="I43"></A><A NAME="I44"></A><A NAME="I45"></A><A NAME="I46"></A><A NAME="I47"></A><A NAME="I48"></A><A NAME="I49"></A><A NAME="I50"></A><A NAME="I51"></A><A NAME="I52"></A>[IndexFile]
<BR></FONT>
<P>
<FONT FACE="Arial">FileSpec_[1...N]<A NAME="I53"></A><A NAME="I54"></A></FONT>
<BLOCKQUOTE>
<P>In SOLID <I>Server</I> data and indexes are stored in the same logical files. The term &#145;index file&#146; is used here as a synonym for the term &#145;database file&#146;. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The FileSpec parameter describes the location and the maximum size of the index file (database file)<A NAME="I55"></A><A NAME="I56"></A><A NAME="I57"></A>. You can use it to define the location and maximum value the index file may grow to.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>You can also use the FileSpec parameter to divide the index file into multiple files and onto multiple disks<A NAME="I58"></A>. To do this, specify another FileSpec parameter identified by the number 2. The index file will be written to the second file if it grows over the maximum value of the first FileSpec parameter. The default value for this parameter is solid.db, 2147483647 (which equals 2 GB expressed in bytes).
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>FileSpec_1=SOLID.DB 2147483647</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>In the following example, the parameters divide the index file on the disks C:, D: and G: to be split after growing larger than 1 GB (=1073741824 bytes).
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>FileSpec_1=C:\SOLID\SOLID.1 1073741824
<BR>FileSpec_2=D:\SOLID\SOLID.2 1073741824
<BR>FileSpec_3=G:\SOLID\SOLID.3 1073741824</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. The index file locations entered must be valid path names in the server operating system! For example, if the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Splitting the index file on multiple disks will increase the performance of the server because multiple disk heads will access the data in your index file. There is no limit to the number of index files you may use. 
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I59"></A><A NAME="I60"></A><A NAME="I61"></A><A NAME="I62"></A><A NAME="I63"></A><A NAME="I64"></A><A NAME="I65"></A><A NAME="I66"></A><A NAME="I67"></A><A NAME="I68"></A><A NAME="I69"></A><A NAME="I70"></A><A NAME="I71"></A><A NAME="I72"></A><A NAME="I73"></A><A NAME="I74"></A><A NAME="I75"></A><A NAME="I76"></A><A NAME="I77"></A><A NAME="I78"></A><A NAME="I79"></A><A NAME="I80"></A><A NAME="I81"></A><A NAME="I82"></A>[General]
<BR></FONT>
<P>
<FONT FACE="Arial">BackupDirectory<A NAME="I83"></A></FONT>
<BLOCKQUOTE>
<P>Backups of the database, log files and the configuration file solid.ini are copied to the backup directory<A NAME="I84"></A>. The default directory &#145;backup&#146; is a directory relative to your SOLID directory. For example if the parameter is
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>BackupDirectory= bu</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>then the backup will be written to a directory that is a sub-directory of the SOLID directory. You may also specify a absolute path name for the directory. For example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>BackupDirectory=e:\backup\solid</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The backup directory must exist and it must have enough disk space for the backup files. It can be set to any existing directory except the database file directory, the log file directory or the working directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. The backup directory entered must be a valid path name in the server&#146;s operating system! For example if the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I85"></A><A NAME="I86"></A><A NAME="I87"></A><A NAME="I88"></A><A NAME="I89"></A><A NAME="I90"></A><A NAME="I91"></A><A NAME="I92"></A><A NAME="I93"></A><A NAME="I94"></A><A NAME="I95"></A><A NAME="I96"></A><A NAME="I97"></A><A NAME="I98"></A><A NAME="I99"></A><A NAME="I100"></A><A NAME="I101"></A><A NAME="I102"></A><A NAME="I103"></A><A NAME="I104"></A><A NAME="I105"></A><A NAME="I106"></A><A NAME="I107"></A><A NAME="I108"></A>[Logging]
<BR></FONT>
<P>
<FONT FACE="Arial">FileNameTemplate<A NAME="I109"></A></FONT>
<BLOCKQUOTE>
<P>Log files are created automatically to the directory specified and by using the filename structure specified by the parameter FileNameTemplate in the Logging section. For example, the following setting
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>FileNameTemplate = d:\logdir\sol#####.log</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>instructs SOLID <I>Server</I> to create log files to directory d:\logdir and to name them sequentially starting from sol00001.log .
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I110"></A><A NAME="I111"></A><A NAME="I112"></A><A NAME="I113"></A><A NAME="I114"></A><A NAME="I115"></A><A NAME="I116"></A><A NAME="I117"></A><A NAME="I118"></A><A NAME="I119"></A><A NAME="I120"></A><A NAME="I121"></A><A NAME="I122"></A><A NAME="I123"></A><A NAME="I124"></A><A NAME="I125"></A><A NAME="I126"></A><A NAME="I127"></A><A NAME="I128"></A>[Sorter]
<BR></FONT>
<P>
<FONT FACE="Arial">TmpDir_[1...N]<A NAME="I129"></A></FONT>
<BLOCKQUOTE>
<P>The TmpDir[1...N] parameter in the Sorter section specifies the directory (or directories) that can be used for the external sorter algorithm which is used for sorting processes that do not fit in main memory. All temporary files used by the external sort are created in this directory (or directories) and are automatically deleted. Setting this parameter enables the use of external sorter.
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I130"></A><A NAME="I131"></A><A NAME="I132"></A><A NAME="I133"></A><A NAME="I134"></A><A NAME="I135"></A><A NAME="I136"></A><A NAME="I137"></A><A NAME="I138"></A><A NAME="I139"></A><A NAME="I140"></A><A NAME="I141"></A><A NAME="I142"></A><A NAME="I143"></A><A NAME="I144"></A><A NAME="I145"></A><A NAME="I146"></A><A NAME="I147"></A><A NAME="I148"></A>[IndexFile]
<BR></FONT>
<P>
<FONT FACE="Arial">CacheSize<A NAME="I149"></A></FONT>
<BLOCKQUOTE>
<P>The CacheSize parameter (the default value depends on the server operating system) defines the amount of main memory the server allocates for the cache. Although SOLID <I>Server </I>is able to run with a small cache size, a larger cache size speeds up the server. The cache size needed depends on the size of the index file, the number of connected users, and the nature of the operations executed against the server. You can view your current CacheSize parameter value with SOLID <I>Remote Control.</I>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I150"></A><A NAME="I151"></A><A NAME="I152"></A><A NAME="I153"></A><A NAME="I154"></A><A NAME="I155"></A><A NAME="I156"></A><A NAME="I157"></A><A NAME="I158"></A><A NAME="I159"></A><A NAME="I160"></A><A NAME="I161"></A><A NAME="I162"></A><A NAME="I163"></A><A NAME="I164"></A><A NAME="I165"></A><A NAME="I166"></A><A NAME="I167"></A><A NAME="I168"></A>[Srv]
<BR></FONT>
<P>
<FONT FACE="Arial">Threads<A NAME="I169"></A></FONT>
<BLOCKQUOTE>
<P>The Threads parameter in the [Srv] section defines the amount of threads the SOLID database engine<I> </I>will use in addition to the communication, I/O and log manager threads. The default value is two threads for database engine use. When SMP support is not enabled the maximum number of threads in the server is limited to 5.
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I170"></A><A NAME="I171"></A><A NAME="I172"></A><A NAME="I173"></A><A NAME="I174"></A><A NAME="I175"></A><A NAME="I176"></A><A NAME="I177"></A><A NAME="I178"></A><A NAME="I179"></A><A NAME="I180"></A><A NAME="I181"></A><A NAME="I182"></A><A NAME="I183"></A><A NAME="I184"></A><A NAME="I185"></A><A NAME="I186"></A><A NAME="I187"></A><A NAME="I188"></A>[SQL]
<BR></FONT>
<P>
<FONT FACE="Arial">Info<A NAME="I189"></A></FONT>
<BLOCKQUOTE>
<P>The Info parameter in the [SQL] section specifies the tracing level on the SQL parser and optimizer as an integer between 0 (no tracing) and 8 (extensive trace outputting). Trace information will be output to the file named soltrace.out in the SOLID directory.
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I190"></A><A NAME="I191"></A><A NAME="I192"></A><A NAME="I193"></A><A NAME="I194"></A><A NAME="I195"></A><A NAME="I196"></A><A NAME="I197"></A><A NAME="I198"></A><A NAME="I199"></A><A NAME="I200"></A><A NAME="I201"></A><A NAME="I202"></A><A NAME="I203"></A><A NAME="I204"></A><A NAME="I205"></A><A NAME="I206"></A><A NAME="I207"></A><A NAME="I208"></A>[Com]
<BR></FONT>
<P>
<FONT FACE="Arial">Trace<A NAME="I209"></A>
<BR></FONT>
<P>
<FONT FACE="Arial">TraceFile<A NAME="I210"></A></FONT>
<BLOCKQUOTE>
<P>These parameters control the outputting of network trace information vital to solving possible network problems. By setting the parameter Trace to the value Yes, SOLID Server starts logging trace information on network messages to the file specified in the TraceFile parameter.
</BLOCKQUOTE>
<A NAME="E10E38"></A>
<P>
<FONT FACE="Arial"><B>Parameter Management</B><A NAME="I211"></A></FONT>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> parameters and their values can be viewed and modified from SOLID <I>Remote Control</I> or by directly editing the solid.ini file in the SOLID directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To View Current Parameter Values Using SOLID </B><B><I>Remote Control</I></B><A NAME="I212"></A></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Connect to the server from SOLID <I>Remote Control.</I>
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Select the Parameters page.
<BR>
<BR>A list of current parameters and their values is displayed.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>The parameters displayed are the parameters currently active in the server. If you have not set a parameter value, the displayed value is the default value for the parameter. The default values are set at start-up and depend on the operating system SOLID <I>Server</I> runs on.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Set a New Parameter Value Using SOLID </B><B><I>Remote Control</I></B><A NAME="I213"></A></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Select from the list the parameter you want to modify.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press Edit or double click the parameter.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Uncheck the Use default box if it is checked.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Enter the new value for the parameter.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press Save to save the parameter value.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P><A NAME="I214"></A><A NAME="I215"></A>NOTE 1. To force a parameter value change to take effect you must shut down and restart the server process.
<BR>NOTE 2. The new parameter values are not checked by the server. Setting an unreasonable value for a parameter may result in an operation failure the next time the server process is started. Do not set a parameter to a random value unless you know what you are doing. Use the default parameter values as an indication on the value range.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E39"></A>
<P>
<FONT FACE="Arial"><B>Constant Parameter Values</B><A NAME="I216"></A></FONT>
<BLOCKQUOTE>
<P>On the PARAMETERS page, some parameters are shown in gray shade. These parameters have constant values. The values were set when the database was created, and they cannot be modified through SOLID <I>Remote Control</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>If you want to use different constant values, you have to create a new database. Before creating a new database, set new constant values by editing the solid.ini file in the SOLID directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The example below sets a new block size for the index file by adding the following lines to the solid.ini file<A NAME="I217"></A>:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>[Indexfile]
<BR>Blocksize=4096</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>After editing and saving the solid.ini file, move the old database and log files, and start SOLID <I>Server</I>. The server program will create a new database with the new constant values from the solid.ini file.
</BLOCKQUOTE><P ALIGN=CENTER>
<A HREF="aguide06.htm" TARGET="_self"><IMG SRC="gaguide/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gaguide/gratop.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gaguide/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="aguide08.htm" TARGET="_self"><IMG SRC="gaguide/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>

<center><p><font SIZE=-2>Copyright &copy; 1992-1997 Solid Information Technology Ltd All rights reserved.</font></p></center>
</BODY></HTML>