1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<HTML>
<HEAD>
<TITLE></TITLE>
<LINK REL="ToC" HREF="httoc.htm">
<LINK REL="Index" HREF="htindex.htm">
<LINK REL="Next" HREF="td000010.htm">
<LINK REL="Previous" HREF="td000008.htm"></HEAD>
<BODY BGCOLOR="#FFFFFF">
<P ALIGN=CENTER>
<A HREF="td000008.htm" TARGET="_self"><IMG SRC="gtd/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gtd/gratoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gtd/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="td000010.htm" TARGET="_self"><IMG SRC="gtd/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>
<A NAME="E64E3"></A>
<H1 ALIGN=CENTER>
<CENTER>
<FONT FACE="Arial"><B>SECTION III </B></FONT></CENTER></H1>
<A NAME="E74E3"></A>
<H1 ALIGN=CENTER>
<CENTER>
<FONT FACE="Arial"><B>MANAGING SOLID </B><B><I>Server</I></B></FONT></CENTER></H1>
<BLOCKQUOTE>
<P>This section concentrates on how to create, configure, and maintain SOLID databases. It also introduces the tools used for problem solving and steps to receive technical support.
</BLOCKQUOTE>
<A NAME="E10E23"></A>
<H2>
<FONT FACE="Arial"><B>SOLID </B><B><I>Server</I></B><B> Database Administration Tasks</B></FONT></H2>
<BLOCKQUOTE>
<P><A NAME="I2"></A><A NAME="I3"></A><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>The deployment and distribution of applications based on SOLID <I>Server</I> technology are as easy as possible. <A NAME="I14"></A><A NAME="I15"></A> SOLID products and services are designed to provide synergy and added value for companies producing mass-marketed software applications and industrial products.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>In a typical client/server configuration, however, the long-term costs are mainly personnel costs. Gartner Group estimates that personnel costs, such as administration and end-user support, account for as much as 85% of the 5-year costs of a project deploying client/server technology. SOLID <I>Server</I> is specifically designed to reduce these costs.<A NAME="I16"></A><A NAME="I17"></A> No heavily trained database administrators are needed. From the end-user's point of view, SOLID <I>Server</I> is virtually invisible.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Installing SOLID </B><B><I>Server</I></B><A NAME="I18"></A><A NAME="I19"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> is simple to install and use: just two to three diskettes and a simple installation program. Only a couple of megabytes of hard disk space are needed for the executable files (SOLID <I>Server</I>, SOLID <I>Remote Control</I> and SOLID <I>SQL Editor</I>). Space allocations for database files, log files, and backup files can be defined dynamically.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><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><A NAME="I27"></A><A NAME="I28"></A><A NAME="I29"></A><A NAME="I30"></A><A NAME="I31"></A><B>Creating a New Database</B><A NAME="I32"></A><A NAME="I33"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>A new database is automatically created when SOLID <I>Server</I> is started and an existing database is not found. During the creation, the database administrator’s user name and password are prompted for. The created database contains the system tables and views and allocates as little as a few hundred kilobytes of disk space.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><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><A NAME="I53"></A><A NAME="I54"></A><A NAME="I55"></A><A NAME="I56"></A><A NAME="I57"></A><A NAME="I58"></A><B>Upgrading and Changing Platforms</B><A NAME="I59"></A><A NAME="I60"></A></FONT></H3>
<BLOCKQUOTE>
<P>Database files are binary compatible between different operating systems. Migration from one operating system to another is simple; just copy the database files to another system, and start SOLID <I>Server</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<IMG SRC="gtd/td000026.gif" WIDTH = 416 HEIGHT = 121 ALT="Undisplayed Graphic">
</BLOCKQUOTE>
<BLOCKQUOTE>
<P><I>Solid’s database file format is binary compatible across platforms.</I>
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><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><A NAME="I83"></A><A NAME="I84"></A><A NAME="I85"></A><B>Database Management</B><A NAME="I86"></A><A NAME="I87"></A></FONT></H3>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> parameters and their values can be viewed and modified either online from SOLID <I>Remote Control</I> or directly by editing the solid.ini file in the SOLID directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><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><B>Disk Management</B><A NAME="I95"></A><A NAME="I96"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID databases can be divided into multiple disk files. The database administrator can specify new database files, i.e., their access path and maximum size, by using SOLID <I>Remote Control</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><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><B>Memory Management</B><A NAME="I109"></A><A NAME="I110"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>There are several parameters that affect SOLID <I>Server’s</I> usage of main memory. Tuning may be necessary to satisfy the needs of critical applications; the default parameter values work well in most cases.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><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><B>User Management</B><A NAME="I123"></A><A NAME="I124"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Users and roles are managed with the SQL2 commands CREATE, DROP, and ALTER. Access rights to data are given to users or roles with the command GRANT.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I125"></A><A NAME="I126"></A><A NAME="I127"></A><A NAME="I128"></A><A NAME="I129"></A><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><A NAME="I149"></A><B>Performance Management</B><A NAME="I150"></A><A NAME="I151"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>New indices can be created to improve query performance with the SQL command CREATE INDEX. Note however, that adding indices makes data modification slower. Also refer to the chapter <I>Problem Solving</I> for information on optimization tools.
</BLOCKQUOTE>
<A NAME="E7E9"></A>
<P>
<IMG SRC="gtd/td000027.gif" WIDTH = 325 HEIGHT = 344 ALT="Undisplayed Graphic">
<BLOCKQUOTE>
<P><I>Even in a distributed, multivendor environment, you can administer the whole database system </I><I>centrally from a single workstation using </I>SOLID<I> Remote Control.</I>
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><B>Checking the State of the Database</B></FONT></H3>
<BLOCKQUOTE>
<P>The state of the database can be verified by running SOLID <I>Server</I> in a checking mode. Depending on the selected mode, different levels of validation checks are performed, and a report is produced.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><B>Continuous Operation</B></FONT></H3>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>7 * 24 Operation</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> is designed to operate in a continuous 7 days by 24 hours mode of operation. Backups and checkpoints can be made online by using SOLID <I>Remote Control</I>. Backups and all changes in the data dictionary can be made during normal operation.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Timed Commands</B><A NAME="I152"></A><A NAME="I153"></A></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> has a built-in timer to automate administration tasks. Timed commands can be used to create backups and checkpoints, disconnect users, and shutdown database servers. These commands may be executed every day or on selected days of the week.
</BLOCKQUOTE>
<A NAME="E10E24"></A>
<H2>
<FONT FACE="Arial"><B>System Programs and Utilities</B></FONT></H2>
<BLOCKQUOTE>
<P><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>The SOLID database management system also includes the following components in addition to the actual SOLID <I>Server</I>:
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I165"></A><A NAME="I166"></A><A NAME="I167"></A><A NAME="I168"></A><A NAME="I169"></A><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><A NAME="I189"></A><A NAME="I190"></A><B>SOLID </B><B><I>Remote Control</I></B></FONT></H3>
<A NAME="E7E10"></A>
<P>
<TABLE >
<TR>
<TD WIDTH=140 VALIGN=top ><IMG SRC="gtd/td000028.gif" WIDTH = 53 HEIGHT = 73 ALT="SOLID Remote Control"><BR></TD>
<TD WIDTH=484 VALIGN=top >
<BLOCKQUOTE>
<P>SOLID <I>Remote Control</I> <A NAME="I191"></A> is a program for the administration of SOLID <I>Servers</I>. It allows you to:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>administer multiple database servers in a network from a single workstation
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>create backups either online or as a timed command
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>obtain server status information</TD></TR></BLOCKQUOTE></UL></TABLE><H3>
<FONT FACE="Arial"><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><A NAME="I209"></A><A NAME="I210"></A><A NAME="I211"></A><A NAME="I212"></A><A NAME="I213"></A><A NAME="I214"></A><A NAME="I215"></A><A NAME="I216"></A><A NAME="I217"></A><B><I>SOLID </I></B><B><I>SQL Editor</I></B></FONT></H3>
<A NAME="E7E11"></A>
<P>
<TABLE >
<TR>
<TD WIDTH=140 VALIGN=top ><IMG SRC="gtd/td000029.gif" WIDTH = 72 HEIGHT = 70 ALT="SOLID SQL Editor">
<BR></TD>
<TD WIDTH=484 VALIGN=top >
<BLOCKQUOTE>
<P>SOLID <I>SQL Editor</I> <A NAME="I218"></A> is a tool for executing SQL queries and commands. It has an easy-to-use graphical user interface. With SOLID <I>SQL Editor</I>, you can:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>use either the interactive or batch mode operation
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>have multiple active connections to various servers
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>save or print query results</TD></TR></BLOCKQUOTE></UL></TABLE><BLOCKQUOTE>
<P><I>Both SOLID </I><I>Remote Control </I>and<I> </I>SOLID <I>SQL Editor</I> are also available as teletype versions<I>.</I>
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I219"></A><A NAME="I220"></A><A NAME="I221"></A><A NAME="I222"></A><A NAME="I223"></A><A NAME="I224"></A><A NAME="I225"></A><A NAME="I226"></A><A NAME="I227"></A><A NAME="I228"></A><A NAME="I229"></A><A NAME="I230"></A><A NAME="I231"></A><A NAME="I232"></A><A NAME="I233"></A><A NAME="I234"></A><A NAME="I235"></A><A NAME="I236"></A><A NAME="I237"></A><A NAME="I238"></A><A NAME="I239"></A><B>SOLID </B><B><I>License Wizard</I></B></FONT></H3>
<A NAME="E7E12"></A>
<P>
<TABLE >
<TR>
<TD WIDTH=140 VALIGN=top ><IMG SRC="gtd/td000030.gif" WIDTH = 52 HEIGHT = 75 ALT="SOLID License wizard"><BR></TD>
<TD WIDTH=484 VALIGN=top >
<BLOCKQUOTE>
<P>SOLID <I>License Wizard</I> <A NAME="I240"></A>is used to update your SOLID <I>Server</I> license. It creates a new SOLID <I>Server</I> license file when you enter the Software Enable Key (SEK) supplied to you in an activation letter.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<IMG SRC="gtd/td000031.gif" WIDTH = 300 HEIGHT = 218 ALT="Undisplayed Graphic"></TD></TR></BLOCKQUOTE></TABLE><BLOCKQUOTE>
<P><I>SOLID SQL Editor is a powerful tool for executing SQL queries and commands.</I>
</BLOCKQUOTE>
<A NAME="E10E25"></A>
<H2>
<FONT FACE="Arial"><B>Configuring SOLID </B><B><I>Server</I></B><A NAME="I241"></A><A NAME="I242"></A></FONT></H2>
<BLOCKQUOTE>
<P>Typically, there is no or very limited need for reconfiguring SOLID <I>Server.</I> For the advanced administrator, however, SOLID offers the possibility to fine-tune the database server operation. The following are the most frequently used database configuration parameters. For more information on configuration parameters, refer to <I>Appendix B Configuration Parameters</I> in <B>SOLID </B><B><I>Server</I></B><B> Administrator's Guide</B>.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I243"></A><A NAME="I244"></A><A NAME="I245"></A><A NAME="I246"></A><A NAME="I247"></A><A NAME="I248"></A><A NAME="I249"></A><A NAME="I250"></A><A NAME="I251"></A><A NAME="I252"></A><B>Database File Locations</B><A NAME="I253"></A></FONT></H3>
<BLOCKQUOTE>
<P>In SOLID <I>Server,</I> data and indices are stored in the same database file. The parameter section name Indexfile is used here as a synonym for the term ‘database file’. The FileSpec parameter describes the location and the maximum size (in bytes) of that database file block . You can use it to define the location of the index file and the maximum size 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. To do this, specify another FileSpec parameter identified by the number 2. The index file will be written to the second file when 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.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Splitting the index file on multiple physical disks will increase the performance of the server because multiple disk heads will access the data in your index file. There is no limit for the number of index files you may use.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I254"></A><A NAME="I255"></A><A NAME="I256"></A><A NAME="I257"></A><A NAME="I258"></A><B>Memory Utilization</B><A NAME="I259"></A></FONT></H3>
<BLOCKQUOTE>
<P>The CacheSize parameter in the IndexFile section defines the amount of main memory (in bytes) that the server allocates for the database cache. Although SOLID <I>Server </I>is able to run with a small cache size, a larger cache size speeds up the server operation. The cache size needed depends on the size of the index file, the number of connected users, and the nature of the operations executed in the server. You can view and edit your current CacheSize parameter value with SOLID <I>Remote Control. </I>This change takes effect the next time SOLID <I>Server</I> is started.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I260"></A><A NAME="I261"></A><A NAME="I262"></A><A NAME="I263"></A><A NAME="I264"></A><A NAME="I265"></A><A NAME="I266"></A><A NAME="I267"></A><A NAME="I268"></A><A NAME="I269"></A><A NAME="I270"></A><B>Multiprocessor Utilization</B><A NAME="I271"></A></FONT></H3>
<BLOCKQUOTE>
<P>The Threads parameter in the Srv section defines the amount of general purpose threads that SOLID Database Engine<I> </I>will use in addition to the communication, I/O manager, and other dedicated threads. The default value is two general-purpose threads for Database Engine operations.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I272"></A><A NAME="I273"></A><A NAME="I274"></A><A NAME="I275"></A><A NAME="I276"></A><B>Backup Files Directory</B><A NAME="I277"></A></FONT></H3>
<BLOCKQUOTE>
<P>Backups of the database, log files, and the configuration file solid.ini are copied to the directory indicated by the parameter BackupDirectory in the General section. The default directory ‘backup’ is a subdirectory in your SOLID directory.
</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 SOLID database directory. Note that the backup directory needs twice the disk space allocated by the actual database files.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I278"></A><A NAME="I279"></A><A NAME="I280"></A><A NAME="I281"></A><A NAME="I282"></A><B>Log Files Directory</B><A NAME="I283"></A></FONT></H3>
<BLOCKQUOTE>
<P>The log files are created automatically by using the filename structure specified by the parameter FileNameTemplate in the Logging section. For example, the following setting:
</BLOCKQUOTE>
<UL>
<P>
<FONT FACE="Courier New">FileNameTemplate = l:\logdir\sol#####.log</FONT>
</UL>
<BLOCKQUOTE>
<P>instructs SOLID <I>Server</I> to create the log files to the directory l:\logdir and to name them sequentially starting from sol00001.log .
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I284"></A><A NAME="I285"></A><A NAME="I286"></A><A NAME="I287"></A><A NAME="I288"></A><B>SQL Trace Level</B><A NAME="I289"></A></FONT></H3>
<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 traceing). Tracing information will be written to the file sqlinfo.out in the SOLID directory.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I290"></A><A NAME="I291"></A><A NAME="I292"></A><A NAME="I293"></A><A NAME="I294"></A><B>External Sorting Directory</B><A NAME="I295"></A></FONT></H3>
<BLOCKQUOTE>
<P>The TmpDir[1...N] parameter in the Sorter section specifies the directory that can be used for the external sorter algorithm when solving complex queries that would require ordering vast amounts of rows.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I296"></A><A NAME="I297"></A><A NAME="I298"></A><A NAME="I299"></A><A NAME="I300"></A><B>Network Names</B><A NAME="I301"></A><A NAME="I302"></A></FONT></H3>
<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.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I303"></A><A NAME="I304"></A><A NAME="I305"></A><A NAME="I306"></A><A NAME="I307"></A><B>Network Traffic Trace</B><A NAME="I308"></A><A NAME="I309"></A></FONT></H3>
<BLOCKQUOTE>
<P>These parameters control the output of network trace information vital to solving possible network problems. By setting the parameter Trace in the Com section to the value Yes, SOLID <I>Server</I> starts logging trace information on network messages to the file specified in the TraceFile parameter.
</BLOCKQUOTE>
<A NAME="E10E26"></A>
<H2>
<FONT FACE="Arial"><B>Solving Problems</B><B> </B><A NAME="I310"></A><A NAME="I311"></A></FONT></H2>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> provides several diagnostic tools for observing the database server performance. These tools, the SQL Info facility and the EXPLAIN PLAN statement, are helpful in tuning your application and identifying any inefficient SQL statements in it.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> also provides tools for tracing the communication between client and server and locating problems that may slow down your application. The Network Trace facility can be used at the server end and the ping facility at the client end.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>For more information on problem solving and the use of diagnostic tools, please refer to <B><I>SOLID Server Administrator’s Guide</I></B>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>SQL Info Facility</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The SQL Info facility is turned on by setting a non-zero value for the Info parameter in the [SQL] section of the configuration file. The output is written to a file named soltrace.out in the SOLID directory. The SQL Info facility can also be turned on and off with the SQL INFO statement.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>EXPLAIN PLAN Statement</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The EXPLAIN PLAN statement is used to show the execution graph that the SQL optimizer has selected for a given SQL statement. An execution graph is a series of primitive operations and a sorting of these operations that SOLID <I>Server</I> performs to execute the SQL statement.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Network Trace Facility</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>By setting the [Com] section parameter Trace in the configuration file solid.ini to the value Yes, SOLID <I>Server</I> starts logging trace information on established network connections to the default trace file or to the file specified in the TraceFile parameter. These messages contain information about:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>loaded DLLs
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>network addresses
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>possible errors
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Ping Facility</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The Ping facility can be used to test the performance and functionality of the network communication. The Ping facility is built in all SOLID clients and is turned on with the network name option -p<I>level</I>. The output of the Ping facility is written into the working directory of the client application. The output file name is specified either by using the parameter TraceFile, the environment variable SOLTRACEFILE, or with the network name option
<BR>-o<I>filename</I>.
</BLOCKQUOTE>
<A NAME="E10E27"></A>
<H2>
<FONT FACE="Arial"><B>Getting Technical Support</B><A NAME="I312"></A><A NAME="I313"></A></FONT></H2>
<BLOCKQUOTE>
<P>Technical support is available from SOLID distributors; all your problem reports should be delivered to your SOLID distributor.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> offers sophisticated diagnostic tools and methods for producing high-quality problem reports with very limited effort. Use the diagnostic tools to capture all the relevant information about the problem.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>For more information on getting technical support, please refer to <B>SOLID </B><B><I>Server</I></B><B> Administrator’s Guide</B>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Before sending a problem report, please also check SOLID Online Services<I>:</I>
<BR> <B>http://www.solidtech.com/</B>
<BR>Your problem may already be solved or at least be known to exist. In any case you may obtain instructions on how to fix or avoid the problem in the future.
</BLOCKQUOTE>
<A NAME="E7E13"></A>
<P ALIGN=CENTER>
<A HREF="td000008.htm" TARGET="_self"><IMG SRC="gtd/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gtd/gratoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gtd/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="td000010.htm" TARGET="_self"><IMG SRC="gtd/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>
<center><p><font SIZE=-2>Copyright © 1992-1997 Solid Information Technology Ltd All rights reserved.</font></p></center>
</BODY></HTML>
|
