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.
The deployment and distribution of applications based on SOLID Server technology are as easy as possible. SOLID products and services are designed to provide synergy and added value for companies producing mass-marketed software applications and industrial products.
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 Server is specifically designed to reduce these costs. No heavily trained database administrators are needed. From the end-user's point of view, SOLID Server is virtually invisible.
SOLID Server 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 Server, SOLID Remote Control and SOLID SQL Editor). Space allocations for database files, log files, and backup files can be defined dynamically.
A new database is automatically created when SOLID Server is started and an existing database is not found. During the creation, the database administrators 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.
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 Server.
Solids database file format is binary compatible across platforms.
SOLID Server parameters and their values can be viewed and modified either online from SOLID Remote Control or directly by editing the solid.ini file in the SOLID directory.
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 Remote Control.
There are several parameters that affect SOLID Servers usage of main memory. Tuning may be necessary to satisfy the needs of critical applications; the default parameter values work well in most cases.
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.
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 Problem Solving for information on optimization tools.
Even in a distributed, multivendor environment, you can administer the whole database system centrally from a single workstation using SOLID Remote Control.
The state of the database can be verified by running SOLID Server in a checking mode. Depending on the selected mode, different levels of validation checks are performed, and a report is produced.
7 * 24 Operation
SOLID Server 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 Remote Control. Backups and all changes in the data dictionary can be made during normal operation.
SOLID Server 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.
The SOLID database management system also includes the following components in addition to the actual SOLID Server:
Both SOLID Remote Control and SOLID SQL Editor are also available as teletype versions.
![]() |
|
SOLID SQL Editor is a powerful tool for executing SQL queries and commands.
Typically, there is no or very limited need for reconfiguring SOLID Server. 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 Appendix B Configuration Parameters in SOLID Server Administrator's Guide.
In SOLID Server, 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.
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.
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.
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 Server 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 Remote Control. This change takes effect the next time SOLID Server is started.
The Threads parameter in the Srv section defines the amount of general purpose threads that SOLID Database Engine 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.
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.
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.
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:
FileNameTemplate = l:\logdir\sol#####.log
instructs SOLID Server to create the log files to the directory l:\logdir and to name them sequentially starting from sol00001.log .
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.
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.
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.
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 Server starts logging trace information on network messages to the file specified in the TraceFile parameter.
SOLID Server 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.
SOLID Server 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.
For more information on problem solving and the use of diagnostic tools, please refer to SOLID Server Administrators Guide.
SQL Info Facility
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.
EXPLAIN PLAN Statement
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 Server performs to execute the SQL statement.
Network Trace Facility
By setting the [Com] section parameter Trace in the configuration file solid.ini to the value Yes, SOLID Server 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:
- loaded DLLs
- network addresses
- possible errors
Ping Facility
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 -plevel. 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
-ofilename.
Technical support is available from SOLID distributors; all your problem reports should be delivered to your SOLID distributor.
SOLID Server 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.
For more information on getting technical support, please refer to SOLID Server Administrators Guide.
Before sending a problem report, please also check SOLID Online Services:
http://www.solidtech.com/
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.
Copyright © 1992-1997 Solid Information Technology Ltd All rights reserved.