Connecting to SQL Databases |
Virtual Machine |
PROIV Functions can access SQL databases as PROIV Files.
The setup is a combination of installation and post-installation processes. The installation allows PROIV to connect to a single SQL database after installation. Procedures in this section allow PROIV to connect to multiple heterogeneous databases.
The following information must be provided to PROIV to ensure successful connection to a SQL database.
File Type - All currently supported database types are allowed.
Connection string - The connection information to the database. For example, the Oracle connection string consists of userid/password@host-string as in:
pro4user/pro4pwd@t:pro4:orcl
DLL Name - Each database access sub-module is created as a DLL (Dynamic Load Library). Where there are multiple versions, the DLL name must be provided to PROIV. This information is provided in the initialisation file using the 'ORACLE_DLLNAME=' environment option. For details about how PROIV accesses databases, refer to the SQL section of PROIV Environment Guide.
Initialisation File - The Windows NT Server kernel looks at two initialisation files.
Global initialisation file - pro4v[n].ini located in the Windows directory.
User specific initialisation file, which can be located in any directory. One file per user is allowed.
The location of the user specific initialisation file must be specified in the user section of the global initialisation file. The user-specific initialisation file can contain user-specific environment settings and logical database path settings. The user specific file should not contain a [USER] section, and if one exists, the contents are ignored.
Click here to learn more about SQL database specific commands that are interrogated in both initialisation files.
Topic ID: 750009