| Actian Zen (PSQL) | |
| Developer: | Actian Corporation |
| Genre: | DBMS, RDBMS, NoSQL |
| Latest Release Version: | v15 SP2 (15.20) |
| Latest Release Date: | August 15, 2021 |
| Language: | English, Japanese |
| Operating System: | Cross-platform |
| License: | Shareware |
Actian Zen (formerly Btrieve, later named Pervasive PSQL until version 13) is an ACID-compliant, zero-DBA, embedded, nano-footprint, multi-model, Multi-Platform database management system (DBMS).[1] It was originally developed by Pervasive Software, which was acquired by Actian Corporation in 2013.[2]
It is optimized for embedding in applications[3] and is used in several different types of packaged software applications offered by independent software vendors (ISVs) and original equipment manufacturers (OEMs). Zen runs on system platforms that include Microsoft Windows, Linux, and Mac OS X. Both 32-bit and 64-bit editions of Zen 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.
Pervasive Software was acquired by Actian Corporation in 2013.[2] Zen is embedded by OEMs like Sage,[4] 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.”[5] The accounting industry formed a large part of its market in 2007.[5]
Historically, Zen served as a DBMS for small and medium enterprises.[6]
Zen supports stand-alone, client-server, peer-to-peer[7] and software-as-a-service (SaaS)[8] architecture.
The central architecture of Zen consists of two database engines: (1) the storage engine, known as MicroKernel Database Engine (MKDE) and described 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.[9]
The Micro-Kernel Database Engine, the transactional database engine, interacts directly with the data and does not require a fixed data schema to access the data. It uses a key-value store to store and access the data. Calls to the MKDE are made grammatically with Btrieve API[7] rather than through the use of a query language; therefore, Zen does not have to parse the request. This places the Micro Kernel Database Engine in the category of NotOnlySQL databases.[10] 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 Zen performance for their applications.
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. Significant other features include relational integrity, database security, and temporary tables. SRDE extends its functionality by supporting stored procedures, user-defined functions, and triggers.[11]
In addition to its support for SQL-92, the SRDE supports several significant features of COBOL: COBOL data types, COBOL OCCURS and VARIANT records.[7]
Zen interfaces fall into two categories: management interfaces and data manipulation interfaces.
Actian provides the management interfaces Distributed Tuning Interface (DTI)[7] and Distributed Tuning Objects (DTO) and a Component Object Model (COM) adapter pattern (wrapper) for the DTI.[7] 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.[17]
All other interfaces[7] exist for data manipulation purposes.
Actian provides utility software designed to facilitate administration and use of Zen.[7] There are graphical and command line utilities in Windows, Linux, and Mac OS X environments.
Zen Control Center (CC) is the main utility that enables the user to create and manipulate databases and tables, to access servers and clients, to set configurations and properties, and to edit data. Through CC, the user can access a series of other utilities:
There are five editions of Zen:
There are two different licensing models, user-count licensing and capacity-based licensing.[25]
Both Zen Edge Server and Zen Enterprise Server use a user-count licensing model, while Zen Cloud Server uses capacity-based licensing, and Zen Core is royalty-free for developers.
| Release | General availability | End of Enterprise Support | End of Extended Support | End of Obsolescence Support | Notes | |
|---|---|---|---|---|---|---|
| August 15, 2021 | TBD | TBD | TBD | Performance Improvements (File Close Delay, Transaction Log Changes, SQL DELETE and LIKE Operations, Scalar Subqueries and Statistics), System Data v2, File Size Limit for Backward Compatibility, SQL Windowing Functions, Administrative Changes, API Updates (Btrieve 2 Improvements, PDAC/BPL Changes, ADO.NET Changes, ActiveX and OLEDB SDK's removed), Platform Changes (removed support for Windows 7 and Windows Server 2008, added support for Windows 10 IoT Enterprise, Windows 11 and Windows Server 2022), Config-on-Install.[28] | ||
| August 27, 2019 | TBD | TBD | TBD | Complete Rebranding, AutoTimestamp Key Type, AES-256 Encryption, Java Runtime Environment Upgrade, JSON Filter, ADO.NET 4.4 Support (including support for Visual Studio 2019 and BIGIDENTITY data type), New Time Data Types (TIMESTAMP2, SQL support for the AUTOTIMESTAMP type, new time scalar functions), New Data Export Tool, Delete Extended Operations, SQL on Android/iOS, Read-Only DSN's, BUTIL Improvements (maintenance utility)[29] |
| Release | General Availability | End of General Availability | Transition Support | End of Support | Notes | |
|---|---|---|---|---|---|---|
| June 23, 2017 | December 31, 2020 | December 31, 2021 | December 31, 2022 | Support for Larger Data Sets, PSQL Reporting Engine, New Btrieve C and C++ APIs, New Schema Export and Import in CC, Updated Cache Management, New SDKs, LIKE with Btrieve Extended Operations, Integration with AD Security, New Operating System Support (Android, iOS, Windows Server 2019, and Windows Nano Server), 8-Byte AutoInc/BIGIDENTITY, TRY_CAST and TRY_CONVERT, UPSERT Capability.[30] | ||
| February 9, 2016 | Not Scheduled | Not Scheduled | Not Scheduled | Btrieve 12 engine is file format and API compatible with Btrieve 6.15, so there is no need to change or even recompile your application. It offers a number of improvements over v6.15, such as full OS support for Windows 7, 8, and 10, improved performance due to a better caching configuration, the ability to use across-the-wire encryption and auto-reconnect (to survive brief network outages on wireless networks), and a vastly simplified configuration.[31] | ||
| December 17, 2014 | June 30, 2018 | January 1, 2019 | July 1, 2019 | Online Database Defragmenter, More Unicode Support, Rebranding, Easier Installation, License Changes, Developer-Level Updates (ADO.NET v4.1 drivers, new features through JDBC and ODBC) New Operating systems (Windows 10, Mac OS X, Windows Server 2016).[32] | ||
| February 9, 2012 | June 30, 2015 | January 1, 2016 | July 1, 2016 | Hypervisor-Friendly Licensing (per instance), Flexible Bit Level Licensing, Optimized Backup Solutions for Virtual Machines.[33] | ||
| September 29, 2010 | June 30, 2015 | January 1, 2016 | July 1, 2016 | New Operating Systems (Windows 8 and Windows Server 2012), Improved multi-threading, Full 64-bit and IPv6 Support, Developer-Level Updates, New Security Solutions and SQL Features, License and Logging Enhancements, Native Backup Solutions (at no extra costs), Licensing Changes and Updated Tools.[34] | ||
| September 18, 2007 | March 31, 2011 | September 1, 2011 | March 1, 2012 | SQL syntax enhancements, a new cache (called Xtreme I/O) to improve 32-bit server performance, and a new 64-bit engine to provide native 64-bit support on newer hardware and operating system platforms. | ||
| March 1, 2005 | July 1, 2009 | July 1, 2009 | January 1, 2010 | Larger Database Support, Improved Linux Support, Improved SQL Performance and Syntax, New DBA Features, A New Control Center, Improved COBOL Support, Drive Letter Redirection, New Developer Features.[35] | ||
| November 26, 2002 | July 1, 2006 | December 31, 2006 | Improved Btrieve and SQL Performance, New SQL Syntax, No More Workstation Engine, New File Format, Simpler Configuration, Debug Requesters, Simpler Licensing.[36] | |||
| September, 1999 | January 1, 2003 | July 1, 2004 | Pervasive.SQL 2000i was available in 3 client/server flavors and two local engines. | |||
| January, 1998 | January 1, 2002 | January 1, 2002 | Pervasive.SQL 7 is the result of the bundling of Btrieve 7 and Scalable SQL 4 (a relational database product) engines into a single product. It allowed for a high level of backward compatibility for applications based on the Btrieve API or ODBC/SSQL. Pervasive.SQL 7 was available in a client/server model for both Novell NetWare and Microsoft Windows NT 4.0, and supports access from DOS, Windows 3.x, Windows 9x, Windows NT, and OS/2 clients.[37] | |||
| July 1, 1994 | July 1, 1999 | September 1, 1999 | See Btrieve for more information. Btrieve 6.15 was released for DOS, Windows and OS/2. This version is incompatible with previous releases, as it was totally rewritten. |
| Release | General Availability | End of General Availability | Transition Support | End of Support | Notes | |
|---|---|---|---|---|---|---|
| August 15, 2021 | TBD | TBD | TBD | AuditMaster v15 offers compatibility with Actian Zen v15.10 for Windows. | ||
| August 27, 2019 | TBD | TBD | TBD | AuditMaster v14 offers compatibility with Actian Zen v14.10 for Windows, and it has been completely rewritten from the ground up with all new tools and alert capabilities. | ||
| June 23, 2017 | December 31, 2020 | December 31, 2021 | December 31, 2022 | AuditMaster v13 offers compatibility with Actian Zen/PSQL v13 and Zen Vx Server 13 Service Pack 1 and newer. | ||
| December 17, 2014 | June 30, 2018 | January 1, 2019 | July 1, 2019 | AuditMaster v12 offers compatibility with Actian PSQL v12 and PSQL Vx Server 12 Service Pack 1 and newer. | ||
| February 9, 2012 | July 1, 2016 | January 1, 2017 | July 1, 2017 | AuditMaster v8.0 offers compatibility with Actian PSQL Vx Server 11 as well as Actian PSQL v11. This version offers a per-database licensing (instead of per user), and worked with 32-bit and 64-bit server engines. Version v8.1 offered compatibility with Service Pack 3 of both PSQL versions, which now included support for Windows 8 and Windows Server 2012. Since v8.0, AuditMaster is only available for Windows. | ||
| November 22, 2010 | April 1, 2012 | January 1, 2016 | July 1, 2016 | AuditMaster v7.0 was released in November 2010 and requires Pervasive PSQL v11. There was only a Windows 32-bit implementation of this product, so it was not compatible with a 64-bit engine. | ||
| September 18, 2007 | October 31, 2011 | March 1, 2012 | September 1, 2012 | AuditMaster v6.4 was supported on Pervasive PSQL v10, and was available for Windows only. This product worked with 32-bit versions of PSQLv10 only. | ||
| November 15, 2005 | March 1, 2010 | March 1, 2010 | October 1, 2010 | AuditMaster v6.3 was supported on Pervasive PSQL v9.1 server database engines only, but there was a version for Windows Servers and a different one for NetWare servers. | ||
| December 31, 2006 | AuditMaster v6.2 was supported on Pervasive.SQL V8 Windows Server database engines only. Workgroup Engines are NOT supported. If you have Pervasive.SQL V8, you can't upgrade to 6.3 - you must upgrade to PSQLv9 first.[38] |
| Release | General Availability | End of General Availability | Transition Support | End of Support | Notes | |
|---|---|---|---|---|---|---|
| January 24, 2023 | TBD | TBD | TBD | DataExchange v15 was designed for Actian Zen v15 Server and Zen Cloud Server 15 systems that are running Service Pack 1 or above. Note that this release includes only the 64-bit Windows platform, so there is no version that will work with a Workgroup Engine. | ||
| May, 2021 | TBD | TBD | TBD | DataExchange v14 was designed for Actian Zen v14 Server and Zen Cloud Server 14 systems. Note that this release includes only the 64-bit Windows platform, so there is no version that will work with a Workgroup Engine. | ||
| June 23, 2018 | December 31, 2020 | December 31, 2021 | December 31, 2022 | DataExchange v13 was designed for Actian Zen v13 Server and Zen Vx Server 13 systems. | ||
| December 17, 2014 | June 30, 2018 | January 1, 2019 | July 1, 2019 | DataExchange v12 was designed for Actian PSQL v12 Server and PSQL Vx Server 12 systems. It features no major changes over v5.1, except for support on Windows Server 2016 and Windows 10. | ||
| February 9, 2012 | July 1, 2016 | January 1, 2017 | July 1, 2017 | DataExchange v5.0 was released to add compatibility with Actian PSQL Vx Server 11 as well as Actian PSQL v11. This version offered a per-database licensing (instead of per user), worked with 32-bit and 64-bit server engines, and was available only for Windows. Version v5.1 was designed for Actian PSQL Server v11 and PSQL Vx Server 11 for Service Pack 3 and newer. This new patch adds support for Windows 8 and Windows Server 2012, but it also removes the DataExchange Designer from the code. | ||
| November 22, 2010 | April 1, 2012 | January 1, 2016 | July 1, 2016 | DataExchange v4.0 required Pervasive PSQL v11. There was both 32-bit and 64-bit versions, and it was only available for Windows. | ||
| August 19, 2008 | October 31, 2011 | March 1, 2012 | September 1, 2012 | DataExchange v3.0 for new PSQLv10 installations was released with Service Pack 1. It only worked on Pervasive PSQL Summit v10.10 and above (it didn't work on v10.00). This tool was supported on Windows 32-bit platforms only. DXv3 did not work on a PSQLv10 64-bit engine. | ||
| September 18, 2007 | August 19, 2008 | August 19, 2008 | September 1, 2012 | DataExchange v2.9 was supported on Pervasive PSQL v10.00, but only as an upgrade from a PSQLv9 installation. This product worked with 32-bit versions of PSQLv10 only. | ||
| April 26, 2005 | March 1, 2010 | March 1, 2010 | October 1, 2010 | DataExchange v2.8 was supported on Pervasive PSQL v9.1 and newer server database engines on Windows servers only (There is no DataExchange for Linux or NetWare). | ||
| December 31, 2006 | DataExchange v2.7 was supported on Pervasive.SQL V8 Windows Server database engines only. If you have Pervasive.SQL V8, you can't upgrade to 2.8 ― you must upgrade to PSQLv9 first.[39] |
Actian Zen lacks: