Pervasive Tips and Tricks

Pervasive Cleanup Utility

Minimize

Pervasive Netware Installation

   Minimize

Recommended Steps Installing the Pervasive Database Engine on the Netware Platform.

1) At the server console type bstop---Most components will unload (ok that some don't)

2) From a PC with admin privilages run the pervasive netware server installation wizard.

3) at the server console type mgrstart

4) at the server console type bstart

5) Install pervasive WGE on the admin PC

6) Use Pervasive Control Center--connect to server and configure settings of server engine Per BS&A recommendations.

7) Add mgrstart at or toward the bottom of the autoexec.ncf (usually done through nwconfig)

8) Down/Restart server.

9) After server reloads from the server console type modules nwmkde.nlm---This should display the nwmkde.nlm if loaded and it's version number (should be 8.6 or 9.1)

10)  Connect to server with pervasive monitor and check settings/lic.

Pervasive/BS&A and ODBC

   Minimize

BS&A Software & ODBC

BS&A Software uses the Pervasive database engine.   One of the unique traits of Pervasive is that the structure of the data file is not kept in the data itself.  It is for the program, stored in the executable.   Any attempt to access the data outside the program necessitates three things.    You must have:

1) The pervasive 7.x or newer drivers installed.  This is either provided or re-sold by BS&A depending on size.  It would be available elsewhere but  due to cost...it is recommended  that they are purchased through BS&A.

2)  The Data Dictionary Files (ddf's--define the structure of the data for the driver).  These are resold by BS&A and not available elsewhere.

3) Data Source Name--DSN's are created to join the exact driver with the particular ddf and a specific data source.  These are created in windows 2000 or Windows XP by the following:

1. Click on start, go to settings and click on control panel
2. Double click Administrative Tools
3. Double click on Data Sources (ODBC)
4. Click on the system dsn tab
5. Click on the add button
6. Scroll to the bottom and select the pervasive ODBS Engine Interface and click finish
7. Type in the data source name
8. Click the create button
9. Enter the database name, the location of the ddf's and the location of the data and click ok
10. Click yes
11. Click test
12. If connection was good as it should be click ok
13. Click ok to close the ODBC

Once this has been done you should be able to access the data in any odbc compliant application (MS Access, or most GIS  programs come to mind) by referencing the DSN.

 

Pervasive SQL and Security

Minimize

Local Security has historically not been an issue with Windows 9.x but can become so as you roll out Windows NT based systems (including Windows 2000 and Windows XP).   If as an administrator you find the need to restrict users (not allowing for local administrator access)--The following changes are required for proper operation of  the Pervasive/BS&A Software suite.  

   1)  Read/write/change or modify access is required at the file level for the local \PVSW\bin directory as well as any program directory storing databases locally (i.e. \equalw) .  

   2)  Permissions on registry hives will need to be changed.  At a minimum, users will need to have read\write\modify access to the HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\    key.  This needs to be set through regedt32.

Windows  Server Level Security requires only read\write\modify access for the Services group to the \PVSW\bin directory, and appropriate file security on the database files themselves.