For those of you who are still on Pervasive 2000i here is some information you need to know.
 
1: 2000i is no longer supported by Pervasive.  The patches and updates have been removed.  If you change servers, you no longer have access to the service packs.
 
2: Pervasive 2000i will not work on Vista.  There is not enough security in the 2000i drivers to use without compromising security.
 
3: Pervasive 2000i will not work with Windows server 2008 (longhorn)
 
4: Pervasive 2000i will not work reliably with Terminal services or Citrix.
 
5: There is no way to add licenses to 2000i.  you must upgrade.
 
So do I need to upgrade?
It will depend on what you are doing and what you plan on doing down the road.
If your company is not growing, you don’t plan on adding PCs or upgrading your server, not using advanced ODBC then you can stay with Pervasive 2000i.  However, if you are planning to do any of the above in the future you will have to upgrade.
 
So what do I need to upgrade to?
 
Pervasive 9.5 will work fine for now but it was not designed for some of the new technologies that are becoming prevalent on the market today. Pervasive 9.5 is the last version to support Netware.   For example, in a terminal service or citrix environment, each session has it’s own set of drives that load and data caching can’t be used because Pervasive gets lost with which session the heap belongs.  Also Pervasive 9.5 is still a proprietary ODBC engine which means some of the advance ODBC SQL commands will not work.  Pervasive 9.5 also uses old DOS path and file names that restrict where pervasive can be installed (that’s why it installs in the root of C: under PVSW) and the size of table, field, function, view, procedure and trigger names.  Pervasive 9.5 is also not designed for the security system within Vista and Longhorn so you have to compromise the system.  Version 9.5 is also limited in its functionality on virtual servers and services.  If you plan on virtualizing and using pervasive, your virtual session must be permanent and not dynamic.
 
Pervasive 10 (Summit) cover many of the new technologies being released today.  It was designed for Vista and Longhorn.  When the client is installed on a machine with terminal services, it installs into the kernel stack to allow complete caching, roll forward and cache sharing within the terminal sessions vastly speeding up data access in a terminal environment.  This same technology is used to allow dynamic virtualization through VMWare or Microsoft Virtual server.  ODBC is also completely compliant and long path and file names are allowed (version 10 actually installs in c:\program files\pervasive\pvsw and c:\documents and settings\All Users\application data\pervasive\pvsw)
 
The biggest issues with updating the Pervasive 10 are as follows:
 
1: Version 10 no longer supports Netware (it does support suze Linux)
 
2: Before upgrading,  you must remove your ODBC connections and previous version of Pervasive.  This is not a Pervasive problem but a Microsoft installer issue between OBDC and the registry.
 
The great news is that Lynn is a licensed reseller of Pervasive and can give you the best price on an upgrade since she is a bulk reseller and a developer.

Probably none for now.  There are file size limitations with 2000i that you could bump up against if you don't keep up on your maintenance. There are not a whole lot of security issues with 2000i.  It's mostly just resource limitations you may run into at some point, and no support for bug fixes or issues that come up should you update a program that relies on PSQL.  The only reason why we updated to 9.5 was we needed to increase our license count and could not do that with 2000i since it was no longer available.  Our 2000i licenses were not compatible/transferrable to a new PSQL version.
 
Val