The only currently supported versions of Pervasive.SQL (by Pervasive) are 11.0 - 11.3 (11 SP3) and 12.
Pervasive.SQL 10.3 (aka version 10 with Service Pack 3) and higher are the only versions of the database that are supported by Pervasive for use with Windows 7. Service Pack 3 is a free upgrade for version 10.0/10.1/10.10/10.2; 10.3 replaces the current license key activation/registration mechanism with a more cumbersome online activation that is tied to the existing hardware, which will require de-/re-activation whenever the hardware is changed. It appears that version 10 installations upgraded to 10.3 keep the old activation mechanism.
Pervasive.SQL 10.2 and earlier were never supported by Pervasive with Windows 7. Version 10.x and earlier are no longer supported by Pervasive on any platform. Pervasive did not release any new versions for Netware after 9.5 but did extend support for 9.5 on Netware until the end of 2014.
These older versions may work on Windows 7 but there are likely to be issues that cannot be fixed, and compatibility will degrade further with future Windows operating system releases. Therefore Support4Omega cannot guarantee Omega will work on these database/OS combinations and does not officially support such combinations, although reasonable effort will be made to overcome any issues.
To complicate matters further two other factors need to be taken into account:
- Pervasive.SQL 10.x requires Windows 2000 SP4, XP SP3, Vista SP1 or Windows 7; Pervasive.SQL 11 drops support for Windows 2000; Actian PSQL 12 (released in December 2014) drops support for Windows XP.
- Different versions of the workgroup engine do not work together; mixing different versions of the client and server usually works for Omega if an older client accesses a newer server engine (Pervasive does not advise this but says that it will probably work; newer clients with older server engines are less likely to work). However relational access, e.g. ODBC/JDBC will generally not work when the version of the client and server differ.
At this stage, Support4Omega offers the following suggestions for sites looking to introduce Windows 7:
- If you are using Windows NT/98 or earlier as Pervasive.SQL clients, and using Pervasive.SQL 9.5 or earlier - test the older client on Windows 7 to see if it is functional with Omega for the short term. It is recommended that you plan on upgrading the server engine to 10.3 if you have Windows 2000 SP4 clients, or 11 if you do not, and therefore test the newer engine against Windows 7 PCs with the 10.3/11 client. Then test the existing PCs, with the older client, against the 10.3/11 server - if these still work you can continue for the short-term with this setup but should start planning on upgrading the Windows 2000/XP/Vista PCs to the 10.3/11 client as soon as possible. Older PCs running Windows 2000 SP3 or earlier have no upgrade path.
Any ODBC/JDBC applications will have to be moved to 10.3/11 clients in order to access the 10.3/11 server. Ideally all PCs will eventually have Windows 2000 SP4 or later.
- If you are running Windows 2000 SP4 or newer as Pervasive.SQL clients, with a Pervasive.SQL 9.5 or earlier server engine - the above suggestion applies again with the recommendation that eventually all PCs are running Pervasive.SQL 10.3 clients against a 10.3 server engine.
- If you are running Windows XP SP3 or newer as Pervasive.SQL clients, with a Pervasive.SQL 9.5 or earlier server engine - as above but with Pervasive.SQL 11 clients against an 11 server engine.
- If upgrading the server engine to Pervasive.SQL 10.3 or later is not an option, e.g. you must stick with a Netware server, you will have no option but to test Windows 7 with Omega and the older client. If this does not work, try using virtualization - some versions of Windows 7 come with Windows XP virtualization (effectively, Virtual PC with an XP image) and you could install the older Pervasive client and Omega within this. Other virtualization solutions are Virtual PC as a separate installation, VMWare Workstation or VirtualBox; another possible solution is Terminal Services.
- For Pervasive.SQL workgroup engine (peer-to-peer) installations, the options are more limited - different versions of the database cannot be used, therefore all PCs must be running 2000 SP4 or newer and Pervasive.SQL 10.3 or newer, or you must stick with the older version of Pervasive.SQL and test its functionality on Windows 7, with or without virtualization. Once again, this is with the understanding that this is not a supported setup even if it appears to work.
|This site is copyright © 2003-2017 Neil Hughes. All rights reserved.|
Company and product names on this site may be trademarks or registered trademarks and are hereby acknowledged.