Printers Software recommends that users use Pervasive.SQL V8.7 or newer for the database behind their application, as these newer versions provide superior performance, reliability, and supportability. If you are experiencing problems with your older environment, then you definitely want to upgrade right away!

QUICK LINKS:

• New Users or Upgrading Users: The current database version is Pervasive PSQL v11. You can Download the 30-Day Evaluation License of Pervasive PSQL v11. For smaller sites (under 5 users), you will want to get the Workgroup Engine. Larger Sites (6+ users) should get the Client/Server Engine, for which the trial will work for up to 20 concurrent users. If needed, you can also download our Installation Document for PSQLv9, which also works for PSQLv10. Our Installation Document is specifically designed to help Printers Software users get the software installed quickly and easily.
• Pervasive PSQL v9 Users: PSQLv9 is an older product that is no longer supported by Pervasive Software. If you are running a version older than v9.71, please should Download the Pervasive PSQL v9.5 Service Pack 2. Once you have done this, download the Pervasive PSQL v9.7x Service Pack 3 Update to get on the latest version. These are free updates for PSQLv9 users. If needed, you can also download our Installation Document for PSQLv9. Our Installation Document is specifically designed to help Printers Software users get the software installed quickly and easily.
• Pervasive.SQL V8 Users: PSQLV8 is an older product that is no longer supported by Pervasive Software. If you are running a version older than V8.7, please Download the Pervasive.SQL V8.7 Service Pack 3. If needed, you can also download our Installation Document for PSQLV8.

Installation of the new engine is easy -- pop in the CDROM & follow the prompts, then reboot, so you can do it yourself or have your tech guy (or gal) handle it for you.

If you have a small site, then the Pervasive WorkGroup Engine (WGE) is for you. While it only supports a maximum of 5 computers (including the server), the WGE is a very cost-effective way to get the benefits of the latest Pervasive database. Note that the WGE is licensed by the number of computers it is installed to. As such, you can license 8 workstations, but remember that only 5 users will be able to run your application at the same time. If you need more concurrent users, then go to the Client/Server Engine.

An upgrade to the Pervasive Server Engine provides the same performance and reliability benefits to larger sites, with user counts of 6, 10, 20, 50, and more. The Server Engine also provides additional performance and security over the WGE, and should be considered even for smaller sites looking to grow in the future. The Server Engine requires the use of a Windows 2000/2003/2008 or Linux database/file server. (PSQLv9 is also available for NetWare Servers.) We recommend making sure that you meet the Pervasive.SQL V8 Pre-Requisites list on your network before upgrading. If you are going with the Server Engine, you'll also be able to use the Backup Agent (to get easier backups), AuditMaster (for independent database auditing), and DataExchange (for replication).

For pricing, please refer to our price list for Pervasive PSQL v11,Buy It Now Online, or contact us for an quote for your exact needs!

Important Note for Windows 95/98/Me/NT/2000 Users: Pervasive PSQL Summit v10 requires Windows 2000 or above to run properly. PSQLv11 requires Windows XP or above. If you have any old computers running older operating systems, you should upgrade these workstations before attempting to switch to PSQLv10 or newer. Windows 7 is supported on v10.30 or above only.

Important Note for DOS Users: Use of native DOS computers with a Windows server is possible, but it requires a technically-challenging configuration. We urge you to consider replacing the workstations with newer boxes to run a Win32 platform instead to cut down on the support costs and configuration time. Goldstar Software can provide support in configuring DOS boxes at our standard support rates.

*The abbreviations used on the columns above include the Workstation Engine (WSE), Workgroup Engine (WGE), and Client/Server Engine (CSE). Not all engines exist in all versions, and these are marked with N/A. Items with a NO are unsupported; items with YES are supported. Items with NR are not recommended; items with R are recommended. Items with no entry are unknown at this time. P indicates that testing is in progress for this release.

Please click HERE for our installation document, which covers the issues of installing Pervasive.SQL V8 for Printers Software environments.

There are eleven points of interest:

1. Performance Tip: If the WGE is used, the machine with the data files physically on it (usually known as the peer server) should be designated as the permanent gateway using the Gateway Locator Utility. (If this is on a separate server, then you will need to purchase a database engine license for this computer as well.) Changing the configuration from a floating gateway (the default) to a permanent gateway will provide the best performance and stability. See our white paper on this topic for more information, or click HERE for the video!
2. Performance Tip: After your system has been running on Pervasive for a few weeks, and you are comfortable enough that you will never go back to the old version, you may want to rebuild your *.PSI data files to take advantage of even more performance gains. See our white paper on this topic for more information. Important Note: Check with PSI before starting this process!
3. Status 116 *OR* Status 20 Problem: We have seen some sites with Status 116 errors after installing, or with Status 20 on the User File. If you run the application and do NOT see the Pervasive.SQL splash screen, then you may have an old DLL still stuck on your system. Search the local and network hard disks to locate a files in the following list: WBTRCALL.DLL, WBTRVRES.DLL, WBTRLOCL.DLL, WBTR32.EXE, WBTRV32.DLL, W32BTICM.DLL, WBTRTHNK.DLL, W32MKDE.EXE, W32MKRC.DLL, dated 1999 or older. If you find such a file, rename or delete it. Do NOT delete any copies in the C:\PVSW\BIN folder. (Copies in the PVSWARCH directory have been found and successfully archived by the installation process. You may leave these copies alone, and after a few weeks, you can safely remove this entire directory structure.)
4. Status 2009 Problem: If you upgrade from Pervasive.SQL 7 to Pervasive.SQL 8, you may get Status 2009. Click here for info on resolving it!
5. Status Code 2738 During Installation: Some users are experiencing this error on certain computers, especially on older Windows 98 computers. This error message indicates that the Microsoft Installer was unable to run the VBScript needed to install the product. If you get this message, you will need to download and install the VBScript update utility from Microsoft, reboot your computer, and then try the installation again.
6. Status Code 161 After Installation: If you are getting a Status 161 (Licensing Error) after installing Pervasive and trying to run with more than 1 user, then your database license may not be properly applied. On each computer, start the Pervasive License Administrator (which you'll find in the Start/Programs/Pervasive programs group) and check the license count showing on this screen. If you see a 1-user license, then you will need to apply your permanent license to this software. See your invoice or packing slip for your Registration Keycode, and enter this number into the boxes provided on that dialog box, then click "Add License". You should see the proper license count then showing.
7. Version Error 8005 / Start Btrieve User: If you are getting this message, then you may have an older version of a critical DLL, specifically WBTRV32.DLL, laying around on your system. Check the local hard disk drive, as well as the PSI directory, for the files indicated in #3 above. If you find OLD versions of these files, please rename or delete them.
8. Problem Printing Reports: If you receive an error printing reports after upgrading to Pervasive, then you need to check to ensure that your PSIDEF.INI file contains the following line anywhere in the section
   marked [Special]:
         TempPath=.\
   Note that this is simply a dot and a backslash, with nothing following it. If you would like your temporary files going into a specific directory (such as H:\TEMP), then you will want to change this to something like:
         TempPath=H:\TEMP\
   Again, you MUST have the trailing backslash in this entry.
   UPDATE: Newer versions of PSI can access this same information by selecting Utilities / Maintenance / Preferences / Multiple Applications / Miscellaneous / Temp Directory and modifying the value there.
9. Status 46: A Status 46 error message has been seen on a few sites that upgraded to Pervasive PSQL v9 but were still running some database files in the archaic Btrieve 5.x file format. The first step is to identify the database file that is still in the older format. To do this, refer to the PSI File List and find the file name that is shown on-screen (right column), as well as the actual file name (left column after the "="). Once you know the file name, use the Pervasive Rebuild Utility to rebuild this file to at least the 6.x file format. For instructions on using Rebuild, please click here. See Note #2 above for more information on rebuilding files.
10. Creating an ODBC Data Source: If you need to create an ODBC data source (for Crystal Reports, UPS WorldShip, or other data access), please see our white paper describing the process. If you need the location of your database files, go to the Utilities / Maintenance / System Control dialog box.
11. Client Cache Engine: Pervasive's Client Cache Engine can be used to sometimes improve performance over some networks. However, the PSI application is not completely compatible with this technology . As such, we recommend disabling the CCE on your server and workstations. On the server, find the configuration setting called "Allow Cache Engine Connections" and make sure it is disabled. On the workstations, find the setting for "Use Cache Engine" and make sure it is disabled. This will prevent additional memory from being used on your workstations and server.