602SQL Documentation Index  

602SQL Installation on Windows

Functional 602SQL installation under Windows can be realized using three procedures:

  1. using 602SQL installation program (everything is usually in a single package 602sqlxx*.exe; only a user with administrator permissions can run this program);
  2. by means of installation program of another product, where 602SQL installation is integrated using so-called installation object (this technique is supported by InstallShield since version 6.0);
  3. by copying 602SQL files to suitable locations and by creation of necessary registry entries.

602SQL installation object is an independently installable product. Its documentation is contained directly in the product. It has its own program interface that allows flexible integration to other installations.

An overview of files and registry entries that are necessary for 602SQL operation is bellow.

Files in the 602SQL Directory

Most files related to 602SQL are copied during installation to a particular directory that will be marked as 602SQL directory. Necessity of these files are related to required 602SQL functions:

Files for fulltext

For fulltext needs (and also for other Software602 programs):

Files in Windows System Directory

Windows system directory contains files that are utilized by other Windows system components, e.g. by ODBC Driver Manager. These are (in version 11.0):

These copies can be substituted by specifying the directory containing the 602SQL installation in the Windows PATH variable.

Registry entry of installation

602SQL version 11.0 installation corresponds to registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Software602\602SQL\11.0

Under this key, following values are found:

Value name Type Meaning Example
Path String Path to the 602SQL directory c:\Program Files\Software602\602SQL
Version String Version number 11.0
FIL version supported String Database file version number 8
Client Protocol String Client network protocol (without server differentiation) TCP/IP

The other possible values are optional.

Registry entry of server and database

For each local database and for each network server, there is a corresponding key in registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Software602\602SQL\Database\name

where name is a database or server name. For example, the Depot database has a key:

HKEY_LOCAL_MACHINE\SOFTWARE\Software602\602SQL\Database\Depot

Under this key, following values are found:

Value name Type Meaning Example Utilized by
Path String Path to the database file D:\db\Depot_db Server
SystemCharset DWORD Server system locale Country code Server
IP address String Server IP address 192.168.1.25 Client
IPPort DWORD Server port number 6000 Client and server
Version String Database file version number 8 Client
Client Protocol String Client network protocol for access to this server TCP/IP Client
Through Firewall DWORD Presence of Socks Firewall between the client and server 0 or 1 Client
Firewall IP address String Socks Firewall Address 192.168.3.115 Client
Use HTTP Tunnel DWORD Use HTTP Communication Tunnel 0 or 1 Client
HTTPTunnelPort DWORD Port number for HTTP tunnel e.g. 81 Client

Socks Firewall address found between the client and server can be also specified jointly for more servers under the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Software602\602SQL

The other possible values are optional.