Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?

In the virtual server environment, it is very easy to adjust the server's memory in order to better suit your requirements and more efficiently use the server hardware.  However, it is important for you to be aware that the PSQL 11 engine license can break if you change the size of the server memory.  In fact, the PSQL 11 engine license can break if any of the following changes occur to the server configuration: 

(1) Server memory size change.
(2) Number of CPU, or the type of CPU change.
(3) Mother board change.
(4) Disk serial number change (this can an issue when your hot swappable RAID drives fail).
(5) The server name is change. 

As you can see, Pervasive implements strict rules to protect their PSQL engine from being copied, and this can be easily done in a virtual environment.  For that reason, we typically suggest that our customers reserve a server with enough memory for future growth so they can avoid changing the memory size down the road when their database grows or some additional task is added to that server. When the PSQL license breaks, fixing it creates an extra burden. So the typical practices involved in dynamically adjusting virtual server memory size or number of CPUs do not work very well with PSQL due to their copy protection scheme. 

If you have to adjust the server hardware configuration (i.e. memory), then it is suggested that you un-register your PSQL 11 engine from your server first.  Then make your adjustment.  Once the server hardware configuration changes are done, register the same key again.

Because Pervasive recognizes these rules are strict, so in PSQL 12, they have dramatically reduce the license checking.  In PSQL 12, as long as you don't change the server name, then the registered license key will not break.  Because of the relaxing of licensing control, PSQL 12 is much suitable to install on virtual server and cloud computing environment. 


Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query
  28. DDF Files in DATA Folder May Confuse PSQL
  29. What to Do When PSQL 11 License Is Disabled
  30. Quick Installation Guide for Audit Master
  31. Quick User Guide for Audit Master
  32. PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider
  33. Your Firewall Needs to Allow Outbound Traffic to the Netherlands for PSQL Licensing Server Purposes
  34. A Case of Btrieve Error 046 on ARCRCLOG A/R Credit Card Log File
  35. A Support Case of Migrating to Different Version of DDF
  36. How to Clear the Message "Unable to Read your Users record (9/068)"
  37. Setup of the PSQL 13 Report Engine
  38. How to Create CPHSTTRX_VIEW with Left Join to CPINVHDR Due to Invoice Database Archive
  39. How to Access Elliott's Data by Using Query in Microsoft Office Excel 2019
  40. Elliott Database Naming Convention
  41. What Does Btrieve Error 080 Mean?

Feedback and Knowledge Base