Pervasive PSQL

Actian Zen (named Pervasive PSQL before version 13) is an ACID-compliant database management system (DBMS)[1] developed by Pervasive Software. It is optimized for embedding in applications[2] and used in several different types of packaged software applications offered by independent software vendors (ISVs) and original equipment manufacturers (OEMs). It is available for software as a service (SaaS) deployment[3] due to a file-based architecture enabling partitioning of data for multitenancy needs.

Actian Zen (PSQL)
Developer(s)Actian Corporation
Stable release
v14.11 / May 2020
Operating systemCross-platform
Available inEnglish, Japanese
TypeDBMS, RDBMS, NotOnlySQL
LicenseShareware
Websitewww.actian.com/data-management/zen-embedded-database/

Applications can store the data and the relationships in tables in a relational model (RDBMS) or store the data in a schema-less way with no fixed data model (key-value store).

Pervasive PSQL runs on system platforms that include Microsoft Windows, Linux, and Mac OS X. Both 32-bit and 64-bit editions of Pervasive PSQL are available. Editions are also specifically designed for different computer networking deployment needs, such as workgroup, client-server, and highly virtualized environments, including Cloud computing.

The original name for Pervasive PSQL was Btrieve.[4] Pervasive Software was acquired by Actian Corporation in 2013.[5]

Uses and customers

Because Pervasive PSQL is used for embedded databases, and sold indirectly, it is not well known.[4] Pervasive PSQL is embedded by OEMs like Sage,[6] maestro* Technologies, ABACUS Research AG (Switzerland), and Unikum (Sweden) in packaged software applications that address the accounting, finance, retail, point-of-sale, entertainment, reservation system, and medical and pharmaceutical industry segments. “Users include Novell, Microsoft, PeachTree Software, Fair Isaac, Disney World, Radio Shack, Cardiff and others.”[7] The accounting industry formed a large part of its market in 2007.[7]

Historically, Pervasive PSQL served as a DBMS for small and medium enterprises.[8]

DBMS architecture
See also: Architecture of Btrieve

Pervasive PSQL supports stand-alone, client-server, peer-to-peer[9] and software-as-a-service (SaaS)[3] architecture.

The central architecture of Pervasive PSQL consists of two database engines: (1) the storage engine, known as MicroKernel Database Engine (MKDE) and described by Pervasive Software as a transactional database engine and (2) the relational database engine, known as SQL Relational Database Engine (SRDE). Both engines can access the same data, but the methods of data access differ.[10]

MicroKernel Database Engine

Pervasive's transactional database engine, the MicroKernel Database Engine, interacts directly with the data and does not require fixed data schema to access the data. It uses key-value store to store and access the data. Calls to the MKDE are made programmatically with Btrieve API[9] rather than through the use of a query language; therefore, Pervasive PSQL does not have to parse the request. This places the MicroKernel Database Engine in the category of NotOnlySQL databases.[11] Low-level API calls and memory caching of data reduce the time required to manipulate data.

The MKDE operates in complete database transactions and guarantees full ACID (Atomicity, Consistency, Isolation, Durability).[1] If a transaction does not fully run its course due to an external event such as a power interruption, the data remains in the state in which it existed before the transaction began to run.

In the MKDE, records are stored in files which are roughly equivalent to the tables of a relational database engine. It supports multiple keys on a record and therefore multiple indexes in the file. The MKDE caches data in memory to facilitate performance. When a call is made to the MKDE, cached data is searched first; physical storage is searched if there is no cache of the data. Configuration settings for caches can be pre-configured by ISVs to optimize Pervasive PSQL performance for their applications.

Relational Database Engine

The second database engine, the SQL Relational Database Engine or SRDE, operates in a manner similar to other relational database engines, that is, through the support of Structured Query Language queries. SRDE parses SQL queries and sends them to the MKDE to run.

The SRDE implements SQL-92.[12] Significant other features include relational integrity, database security, and temporary tables. SRDE extends its functionality by supporting stored procedures, user-defined functions, and triggers.[13]

In addition to its support for SQL-92, the SRDE supports several significant features of COBOL: COBOL data types and COBOL OCCURS and VARIANT records.[9]

Additional features

Pervasive PSQL provides the following additional features:

Interfaces
Interfaces for Pervasive PSQL

Pervasive PSQL interfaces fall into two categories: management interfaces and data manipulation interfaces.

Management interfaces

Pervasive Software provides the management interfaces Distributed Tuning Interface (DTI)[9] and Distributed Tuning Objects (DTO), a Component Object Model (COM) adapter pattern (wrapper) for the DTI.[9] These provide application programming interfaces for configuration, monitoring, and diagnostics of Pervasive components. COBOL can also provide component management through a COBOL connector that can talk to DTI.[19]

Application interfaces

All other interfaces[9] exist for data manipulation purposes.

Tools

Pervasive provides utility software designed to facilitate administration and use of Pervasive PSQL.[9] There are graphical and command line utilities in Windows, Linux, and Mac OS X environments.

Pervasive Control Center (PCC) is the main utility that enables the user to create and manipulate databases and tables, to access servers and clients, to set configuration, properties, and to edit data. Through PCC, the user can access a series of other utilities:

  • License Administrator utility handles license management activities.
  • Notification Viewer utility displays licensing-related messages logged by the PSQL engine.
  • Monitor utility checks and displays activities and attributes of both engines, including resource usage, session information, and communication statistics.
  • Pervasive System Analyzer utility tests the connections between the engines and within the network and displays information about system components.
  • Maintenance utility enables users to create and edit schema-less files.
  • Rebuild utility enables users to convert file formats and rebuild files in its MKDE file format.
  • DDF (data definition file) Builder utility enables SQL users to create and modify table schemas for data stored in the MKDE, thus providing relational access to the data.
  • Query Plan Viewer enables SQL users to analyze query plans for optimization.
  • Function Executor assists developers with development, testing, and debugging by simulating direct API operations into MKDE and providing a view into the schema-less data.

Versions

See Btrieve, beginning with Pervasive.SQL 7.

Editions and licensing

Editions

There are four editions of PSQL:[9] Pervasive PSQL Client, Pervasive PSQL Workgroup, Pervasive PSQL Server, and Pervasive PSQL Vx Server.

  • Pervasive PSQL Client is designed for use with Pervasive PSQL Server and Pervasive PSQL Vx Server in a client-server network.
  • Pervasive PSQL Workgroup edition is intended for single- and multi-engine configurations with up to five users.[20]
  • Pervasive PSQL Server edition is intended for configurations that have at minimum ten concurrent connections and it is scalable up to thousands of concurrent network users in client-server network and web-based applications on the enterprise level.[9]
  • PSQL Vx Server runs under hypervisors in a VM environment. It is designed for customers “who need support for highly virtualized environments enabling live migration, fault tolerance, high availability and cloud computing.”[21]

Licensing

Pervasive Software uses two different licensing models, user-count licensing and capacity-based licensing.[9]

  • In user-count licensing, each product key specifies a licensed user. At any given moment, that many users can be connected to the engine.
  • Capacity-based licensing is based on the amount of processing performed by the database engine. It measures data in use and sessions in use. This license model is designed to facilitate Cloud computing and highly virtualized environments.

Both PSQL Server and PSQL Workgroup use a user-count licensing model, while PSQL Vx Server uses capacity-based licensing.

Limitations

Pervasive PSQL lacks:

  • some of the data warehousing, data mining, and reporting services built into database engines such as MySQL and Microsoft SQL Server.[10]
  • Unicode support in the RDBMS layer.
  • the ability to perform distributed transactions.
  • support for database caching unless the application has specifically been designed to take advantage of the Client Caching Engine(very few applications take advantage of this feature), the inbuilt feature of the engine and only supported caching option. Because the engine does not natively support database contention negotiation but relies on the front-end to manage contention issues, it is infrequently implemented. This makes the majority of applications developed with Pervasive PSQL unsuitable on any system where network or host server performance could cause a performance bottleneck.[22]

See also

References
  1. Wiejers, Ben (October 2001) [December 2000]. "Transactions, Locking and DataFlex". Data Access Worldwide.
  2. Stanley, Nigel; Kaufman, Marcia (2007). "Delivering Embedded Database Solutions for Small and Medium-sized Businesses" (PDF). Hurwitz and Associates.
  3. Bloor, Robin; Jozwiak, Rebecca (December 2011). "Moving to the Cloud with Pervasive PSQL" (PDF). The Bloor Group.
  4. van der Lans, Rick F. (2009). The SQL Guide to Pervasive PSQL. Lulu. pp. 44–45. ISBN 978-0-557-10543-4.
  5. "Actian Corporation and Pervasive Software Unite to Take Action on Big Data".
  6. "Manufacturing ERP Software–Sage PFW ERP". Sagepfw.com. Retrieved 2012-05-12.
  7. Vaughan, Jack (October 16, 2002). "Pervasive on replication trail". Application Development Trends.
  8. "Software provides growth solution for organization databases". ThomasNet News. September 26, 2007.
  9. "Pervasive Documentation Library: Pervasive PSQL v11 SP2". Pervasive Software. April 2012.
  10. Lax, Joe (January 23, 2004). "Top-notch Auditing an Impressive Add-on for Pervasive.SQL". DevX.com.
  11. "LIST OF NOSQL DATABASES". NoSQL. Retrieved April 30, 2012.
  12. Brettski (January 4, 2009). "Methods for interacting with a Pervasive SQL database". stackoverflow.
  13. van der Lans, Rick F. (2009). The SQL Guide to Pervasive PSQL. Lulu. pp. 443–548. ISBN 978-0-557-10543-4.
  14. "What file versions does Row Level Locking (RLL) work with in Pervasive.SQL 2000?". Pervasive Software. June 2001.
  15. "Pervasive Software Delivers Pervasive PSQL Summit v10.10 Database". Pervasive Software. June 11, 2008. Archived from the original on January 31, 2013. Retrieved April 18, 2012.
  16. Durham, Dale (April 23, 2008). "Unicode support?". Pervasive Community Site.
  17. "Pervasive Documentation Library: Pervasive AuditMaster". Pervasive Software. April 2012.
  18. "Pervasive Documentation Library: Pervasive DataExchange". Pervasive Software. April 2012.
  19. "Pervasive Documentation Library: Pervasive PSQL v10" (PDF). Pervasive Software. April 2008.
  20. "Zen Workgroup for Windows and PSQL Workgroup". Actian. Retrieved 8 October 2020.
  21. Beal, Vangie (February 13, 2012). "Pervasive Software Announces Hypervisor-Friendly PSQl Vx Server 11". ServerWatch.
  22. "Making the Most of the Client Cache Engine" (PDF). Goldstar Software Inc. March 7, 2016.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.