9 Reasons to Buy Pervasive PSQL V9

Total Page:16

File Type:pdf, Size:1020Kb

9 Reasons to Buy Pervasive PSQL V9 Product Platforms Highlights Pervasive.SQL Windows, Linux, NetWare Power, Embeddability, Low TCO, Security 9 Reasons to Buy Pervasive PSQL v9 With the release of Pervasive PSQL v9, we have made a number of improve- STRENGTHS: ments to the previous release. With specific improvements to performance, Performance scalability, management, and international capabilities, Pervasive PSQL v9 Embeddability continues to raise the bar for embedded database applications. Low TCO Security Flexibility Improved Performance and Reporting: Easier Development and Management Extensive Standard Support 30 New Performance Optimizations of Applications: Brand New GUI Full Suite Of GUI Utilities Pervasive PSQL v9 includes over 30 separate optimiza- All new Pervasive.SQL Control Center (PCC) has tions that improve performance over previous versions. been rewritten in Java on the Eclipse framework. PCC These optimizations impact all of the SQL interfaces will provide a foundation for all future GUI tools, mean- (ADO.net, JDBC, ODBC, and OLE DB), and the improve- ing that the development and maintenance GUI will be SUPPORTED PLATFORMS: ments result in faster standard and ad-hoc reporting. shared across Pervasive PSQL platforms. • Aggregate queries (those containing GROUP BY • SQL Outline View – provides developers a way to Server clauses) view, dissect, and understand large queries (new • Windows NT 4.0 (SP6a or higher) • Windows 2000/2003 • Sub queries using IN, NOT IN, or =ANY predicates feature) • NetWare 5.1, 6, 6.5 or higher • Sub queries containing expressions • SQL Editor – allows interactive SQL execution from • Linux (Kernel 2.4 or 2.6) • Join queries containing HAVING predicates PCC (replaces SQL Data Manager) • Queries returning multiple rows from a particular • Table Editor – allows you to create & edit tables Client Requestors table using an index from PCC (replaces Table Designer) • Windows NT 4.0* (SP6a or higher) • Forward-only, read-read only cursors • Windows 2000/2003* • Windows 98/ME/XP* • Prepared statement execution Improved Scalability: • DOS 5.0 or higher • INSERT statements that affect a single table Increased Maximum File and Page Sizes • Linux (Kernel 2.4 or 2.6) • Cursor processing Pervasive PSQL v9 offers twice the maximum file size • BLOB/CLOB processing and page file of the previous version. PSQL v9 in- Workgroup/Workstation • Windows NT 4.0* (SP6a or higher) • Transaction logging cludes an ability to retrieve files up to the 128GB maxi- • Windows 2000/2003* mum, reducing the number of archives and improving • Windows 98/ME/XP* Easier Design Process: file management. New SDK Components *Supports DOS, Win 16 and Along with all the tools available on disk or online at ������� ������� Win 32 applications the Pervasive Development Center, the Software ������������� ������ ����� Development Kit for Pervasive PSQL v9 includes: • DDF Builder 4.0: Pervasive PSQL v9 introduces a ��������� �� �� brand new version of the SmithWare favorite, mak- ing it easier for you to describe existing data files for SQL access. Completely redesigned, this version has Reduced Need for Cross-Platform been rewritten in Java on the Eclipse framework. Porting & Management: SQL Functionality, Grammar, and Syntax • Full Text Search (FTS): FTS allows developers to Improvements incorporate text searches in new application develop- We are committed to helping minimize time required to ment. FTS provides Google-like searching of Pervasive. deploy and maintain multiple version of your applica- SQL data including text string, number, date and tions. Pervasive PSQL v9 introduces improvements Boolean searches, support for wild cards, “AND” and to the SQL interface, and improved compatibility with “OR” searches. international standards and other relational DBMSs. >> continued ABOUT PERVASIVE SOFTWARE SQL Functionality All the features of SQL, for use with leg- • Use defined functions – CREATE FUNCTION acy applications without code rewrite: syntax added for user-defined scalar functions COBOL/ISAM Support • System stored procedures Pervasive PSQL v9 is the most economical and safest way • CAST scalar functions – To change data types when to provide SQL access and new features to a legacy ap- selecting a column. Useful for: plication. With the addition of support for ISAM data con- • Concatenating strings structs, Pervasive PSQL v9 provides COBOL developers a • Joining columns that were not initially way to modernize their application with SQL access without Pervasive Software is a global envisioned as related having to redesign, reengineer, or rewrite their code. • Performing mathematical operations value leader in data infrastructure • Variable record layout support – Many ISAM applica- software. The company’s award- on columns that were defined as char- tions utilize multiple record layouts in a single file, which winning products enable customers acter but which contain numbers can present problems for some relational DBMS en- to manage, integrate, analyze and • COALESCE scalar function – Returns the value of gines. Pervasive PSQL v9 provides an enhanced cata- secure their critical data, providing the first non-null expression among the “n” expres- log system that will provide accurate column information the industry’s best combination of sions that are passed to the function as arguments regardless of the irregularity of the record layouts. • – Returns a server process ID of the current performance, reliability and cost. @@SPID • Support for Shifted/Unshifted Numerics – v9 pro- Pervasive’s strength is evidenced thread assigned by the server for each connection vides two settings for updating signed numeric values by the size and diversity of its from the SQL interfaces. This update will allow Fujitsu customer base, serving tens of SQL Syntax and Grammar COBOL applications to use both Btrieve and relational thousands of customers in nearly • Sub queries as expressions – Permit the use of a interfaces. SELECT sub query as an expression every industry market around the • Support for OCCURS – Pervasive PSQL v9 includes world. With headquarters in Austin, • DEFAULT constraints – Permits the use of functions support for the COBOL OCCURS clause in the rela- Texas, Pervasive was founded in such as USER(), CURDATE(), and other expressions tional engine. OCCURS data can be queried as if it 1994 and sells its products into as default constraints for a column were a separate table. • – for AND (&), NOT (~), OR (|), more than 150 countries. Bitwise operators • Support for Partial Redefines – Redefinition of a por- exclusive OR (XOR) tion of data within a record (instead of redefinition of the • NULL in an expression – v9 permits the use of the entire record – variable record layout) NULL keyword as part of an expression • Supports ANSI JOIN Syntax – Makes the specifica- FOR MORE INFORMATION tion of the JOIN type optional Faster Running Applications on the • Complex VIEW Syntax – Whereas v8 restricts the Linux Platform: • To learn more about Pervasive Software and our solutions, syntax of queries that can be defined in a stored view, Improvements for Linux please visit www.pervasive.com. v9 extends the VIEW syntax to overcome these issues Linux performance improvements and a new GUI (in • CASE expression – Enhanced in v9 to produce more Pervasive PSQL v9 SP1) help developers increase • To reach the North American sales office, call 1.800.287.4383, streamlined code their sales potential for applications in the Linux com- extension 2. • EXEC function - Allows invocation of a user-defined munity. Relational and Btrieve access on Linux has been procedure or a stored procedure (the ability to build a improved through the use of common address space • For Latin, Central and South query on the fly in a stored procedure using param- technology, which was previously used only on Windows. America, Australia and New Zealand, call +1.512.231.6000. eters passed in, then execute that stored procedure) Additionally, the Pervasive.SQL JCL has been ported to • EXISTS syntax in sub query in Stored Procedures Linux to provide dual access in Java applications. • In Europe, for Belgium, France, – Pervasive PSQL v9 emulates MS SQL Server syntax Germany, Italy, Luxembourg, The for EXISTS as a predicate of a sub query in a stored Netherlands, Spain, Sweden, procedure (one less hassle to deal with when migrating Reduced ISV Support Costs (Lower Switzerland and the United Kingdom, call +800.12.12.34.34. between the two platforms) TCO): Improved Installation Process • ISNULL – Emulate SQL Server syntax for ISNULL and Compatibility • For any other European, Middle function Better handling of settings conflicts and version-related Eastern, African or Asian coun- tries (excluding Japan), call installation problems, as well as improved networking Easier International Releases: +32.70.23.37.61. further reduce ISV time required to support installations Standards Conformance and updates. Our new high performance bulk data util- • For Japan, please call Pervasive PSQL v9 conforms to ODBC 3.51 (vs. ODBC ity reduces the time required for initial data loading into +81.3.3293.5300, or visit www.pervasive.co.jp. 2.5 in Pervasive PSQL v8), enabling support for Unicode. Pervasive PSQL v9 tables. ©2004 Pervasive Software Inc. All rights reserved. All Pervasive brand and product names are trademarks or registered trademarks of Pervasive Software Inc. in the United States and other countries. All other marks are the property of their respective owners. .
Recommended publications
  • Sage 300 Ops Inquiry and Sales Analysis Database Conversion Guide
    Sage 300 Ops Inquiry and Sales Analysis Database Conversion Guide July 2017 This is a publication of Sage Software, Inc. © 2017 The Sage Group plc or its licensors. All rights reserved. Sage, Sage logos, and Sage product and service names mentioned herein are the trademarks of The Sage Group plc or its licensors. All other trademarks are the property of their respective owners. Last updated: July 5, 2017 Table of contents Introduction 3 System requirements 3 Converting databases to Microsoft SQL Server format 4 Step 1: Activate Ops Inquiry and/or Sales Analysis 4 Step 2: Set up a new Microsoft SQL Server database 4 Step 3: Set up access to your Pervasive database 4 Step 4: Copy data from your Pervasive database to your Microsoft SQL Server database 6 Step 5 (optional): Set up a pictures directory in Ops Inquiry 8 Ops Inquiry and Sales Analysis Database Conversion Guide ii Introduction Beginning in Sage 300 2016, only databases in Microsoft SQL Server format are supported. If you are upgrading from a previous version of Sage 300 and you have Ops Inquiry or Sales Analysis databases in Pervasive format, follow the steps in this guide to convert your databases to Microsoft SQL Server format. Note: You must convert your databases before installing your new version of Sage 300. System requirements To complete the steps in this guide, you must have: • Pervasive PSQL Client or Server • MS SQL Server 2008 or later • SQL scripts provided by Sage: – ActivateData.sql – DisableIndexes.sql – EnableIndexes.sql Ops Inquiry and Sales Analysis Database Conversion Guide 3 Converting databases to Microsoft SQL Server format Follow the procedures in this section to convert a database from Pervasive format to Microsoft SQL Server format.
    [Show full text]
  • Pervasive PSQL V11 4 Optimized for Multi-Core Servers 4 64-Bit Windows ODBC Driver 4 Support for Ipv6 4 ADO.NET 3.5 Provider with .NET Entity Framework Support
    PRODUCT SHEET Pervasive PsQL v11 4 Optimized for Multi-Core servers 4 64-bit windows ODBC Driver 4 support for iPv6 4 aDO.Net 3.5 Provider with .Net entity Framework support 4 PDaC for raD studio 2010 and 2009 Overview Benefits Pervasive PSQL™ is one of the most reliable, low-maintenance, high-performance database management systems (DBMSs) in the world. Pervasive PSQL v11 offers • Multi-core performance without changing important additions — multi-core optimization, enhanced 64-bit support, IPv6 your application support and updated developer tools. • Improved scalability—more users, more cores, more data processing power New Features • Simple transition to IPv6 • More 64-bit relational support Optimized for Multi-core – Pervasive PSQL v11 is a parallel implementation of Pervasive PSQL that includes several enhancements for multi-core: • Updated developer tools • Simple migration from previous versions • Improvements to the low-level synchronization mechanisms in the transactional interface • Multiple users can read the same cached file pages simultaneously and their operations can proceed on multiple cores supported Platforms • Multiple users accessing independent files can proceed on different cores • Windows 7 • Non-user activity such as checkpoint and log management can also use • Windows Server® 2008 and 2008 R2 additional cores • Windows Vista® 64-bit ODBC – Pervasive PSQL v11 supports the ODBC interface on native 64-bit • Windows Server 2003 Windows operating systems with 64-bit architecture. The transactional and relational • Windows® XP interfaces for 64-bit Pervasive PSQL Server are now in the same common address space. • Red Hat® Enterprise Linux 4 and 5 • SUSE™ Linux Enterprise 9 and 10 IPv6 Support – IPv6 (Internet Protocol version 6) is the Internet protocol that will follow • Citrix the current version - IPv4.
    [Show full text]
  • Tested and Supported Environments
    Tested and Supported Hertzler Systems Inc. Turning Data into Knowledge Environments GainSeeker® Suite v9.2 Definitions Tested: Operating systems, networking systems and databases listed as tested are the systems on which Hertzler Systems has extensively tested our program in our test environment. We are confident that our program will operate with normal parameters, in environments using these components, for most users. Supported: Operating systems, networking systems and databases listed as supported are the systems on which we have done little or no in‐house testing recently. Most of these components have been tested on previous releases, but are no longer part of the testing program (due to the march of progress and limited testing resources) or are too new to have been included in the testing program. We feel we can reasonably expect our program to run in environments using these components (in conjunction with other supported or tested components) with no issues. Note: Every reasonable effort will be made to correct any issues that arise in Tested and Supported operating environments. Unsupported: Operating systems, networking systems and databases not listed as tested or supported are considered unsupported at this time. Hertzler Systems makes no assumptions that the program will run in environments containing one or more unsupported components and may not provide customer support services for these environments. If support is provided, it may be a chargeable service, even for customers with support contracts. Systems Tested Operating
    [Show full text]
  • Accessing Zen/PSQL Data from ODBC Or Other Applications
    Accessing Zen/PSQL Data From ODBC Or Other Applications A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Accessing Zen/PSQL Data From ODBC (or Other Applications) Last Updated: 02/23/2021 When it comes to "frequently asked questions", this one takes the cake, to be sure. It seems that people are used to databases which provide ODBC access natively (such as FOXPro, Access, etc.) and get confused when they cannot access their own application data immediately. Then, they start “Btrieve-bashing” because they can't get their data out. This document was created to provide some explanation as to what the issues are when it comes to ODBC access and your data, whether it be stored in a current Actian Zen database engine, or one of the older ones, including Actian PSQL, Pervasive PSQL, Pervasive.SQL, and even Btrieve. The material is taken mostly from the PSQL Service & Support classes provided by Goldstar Software. Database Engine Type & ODBC Drivers The first question we have to deal with is the availability of ODBC drivers. If you have a newer engine, then you can skip this section entirely. If you have an older engine, though, then you should read on. Old DOS applications may be using Btrieve 5.x or older for DOS, 5.x for Windows, or even Btrieve 5.x or 6.10 for NetWare. These engines do NOT contain an ODBC driver and will not support 32-bit ODBC access. (MS Access 2.0 had limited support for Btrieve 6.10, but only from 16-bit Windows applications.) If this is the case, then you will need to purchase a new database engine to support this access.
    [Show full text]
  • Creating an ODBC Data Source for Zen/PSQL
    Creating an ODBC Data Source for Zen/PSQL A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Creating an ODBC Data Source for Pervasive PSQL Last Updated: 02/05/2021 Many users of Actian Zen/PSQL (formerly Pervasive PSQL) see their data through Btrieve-level applications which access the data natively using low-level (and very high- performance) function calls. However, getting access to this data from other applications, such as Microsoft Access, Crystal Reports, UPS WorldShip, and others may require that you configure an ODBC data source for the database engine. There are actually several ways to do this task, depending on the software version you are using. Using the Control Center may be the quickest way to do it, but the screens look different for each engine version. To use this, check with the online manuals regarding the Control Center. Since database versions tend to share a similar interface at the native ODBC level, we will go through the ODBC Administrator to create the database. Create the Engine DSN on the Server Start by logging into the database server at the console itself. If you must use a Remote Desktop or Terminal Services connection, then you may also need to set the registry key HKLM/Software/Pervasive Software/Utilities Interface/Settings/Restricted Access on WTS Client to 0 (unrestricted access), or this may not work correctly. Start the ODBC Administrator from the Windows Control Panel. In newer versions of Windows, this may be located in different locations, such as under Administrative Tools.
    [Show full text]
  • Pervasive PSQL Vx Server Licensing
    Pervasive PSQL Vx Server Licensing Overview The Pervasive PSQL Vx Server edition is designed for highly virtualized environments with support for enterprise hypervisor features including live application migration (moving a virtual machine from one physical server to another while the application remains running), high availability and fault tolerance. As with other Pervasive PSQL products, it is licensed one instance per server (virtual or physical). Where Pervasive PSQL Vx is significantly different from other Pervasive PSQL products is that PSQL Vx licenses are priced by capacity, or how much work can be performed by the database engine. Capacity is measured by two factors: concurrent sessions (connections to the transactional or relational engine) and data in use (total size of the files opened by the database). Pervasive PSQL Vx Server is available in basic configurations – Small, Medium, Large and SuperSize. Session count and data in use limit increases are both available to allow customers to fine tune database capacity. And, unique to Pervasive PSQL Vx Server, time‐limited 60‐day session count and data in use are available to provide an affordable way for customers to meet peak database demand requirements. What’s New in Licensing for Pervasive PSQL Vx Server Pervasive PSQL Vx Server licensing features were designed with two major goals in mind: 1) ensure that PSQL Vx Server authorization and validation processes enable customers to take advantage of enterprise hypervisor features and 2) offer a licensing model relevant to customers delivering applications in public, private or hybrid cloud environments. The following table highlights some of the differences between Pervasive PSQL Vx Server and Pervasive PSQL Server.
    [Show full text]
  • Determining Your Pervasive, Actian, PSQL Or Btrieve Engine Version
    Determining Your PSQL Engine Version A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Determining Your PSQL Engine Version Last Updated: 12/18/2018 It is very common for people to know that they are using the Btrieve or Pervasive PSQL, or Actian Zen database engine, but to not know exactly which version they are using. Moreover, the list of related files is often a mystery, especially for older versions, and some users are simply without a clue as to what modules are part of the database and what are not. This paper was created so that someone could locate the PSQL-related files on their workstation or server and determine the exact version, including user count, where appropriate. NetWare Server Engines With NetWare servers, it is possible to have any version of Btrieve from 5.x all the way through Pervasive PSQL v9. Many users see the version reported from BREQUEST and assume that this is their Btrieve version -- it just isn't so! You must query the server to determine exactly which version of BTRIEVE.NLM you have. On older versions of NetWare, you can do this with the "MODULES" command, which lists all the loaded modules on the server. Then, watch for the BTRIEVE.NLM to scroll by. For NetWare 4.11 and above, you can use the command "MODULES BTR*" to list only those modules that start with "BTR", which will save some searching. With the release of Pervasive.SQL 7, Pervasive Software started including the SQL engine "in the box" with the Btrieve engine.
    [Show full text]
  • Pervasive PSQL Summit V10 Highlights Performance and Analytics
    Pervasive PSQL Summit v10 Highlights Performance and analytics A Monash Information Services Bulletin by Curt A. Monash, PhD. September, 2007 Sponsored by: Pervasive PSQL Version 10 Highlights Page 2 Introduction PSQL v10 features In September, 2007, Pervasive Software is releasing Pervasive PSQL performance gains Summit v10. As befits a major product release, v10 boasts a broad variety of and new analytic enhancements and new features, especially in the areas of performance and functionality. query-related functionality.* Most important, Pervasive is tapping into two major industry trends: 1. More -- and more affordable -- RAM. 2. The growing importance of analytic (as opposed to purely transactional) technology. *There also are important steps in standards compatibility, specifically with several layers of Microsoft operating software, especially Microsoft Vista. But those aren't covered in this paper; please contact Pervasive directly or go to www.pervasive.com for details. XIO accelerates Major releases of a database management system typically boast multiple performance. performance improvements, and PSQL v10 is no exception. Most important are those delivered through a driver called XIO, for “(e)Xtreme I/O.” XIO contains a number of features, but the core idea is this. If you compress data intelligently, you get two big benefits: Less data has to flow from disk, so the system has to do less I/O (this is more relevant to analytics than to transaction processing). More data fits into cache, so the system often doesn't have to do any I/O at all (this is relevant to all kinds of processing). The DDF Builder As well as boosting performance, PSQL boasts significant improvements in eases business relational functionality.
    [Show full text]
  • Btrieve Error Codes 3000 - 3099 ← Pervasive PSQL Microkernel Router Status Codes
    Btrieve Error Codes 3000 - 3099 ← Pervasive PSQL MicroKernel Router Status Codes This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel. 3000: The MicroKernel router encountered a memory allocation error The MicroKernel router could not internally allocate memory. Check the Pervasive Event Log (PVSW.LOG) for more information. 3001: Local access is unavailable to the MicroKernel router A call to the MicroKernel failed. This is most likely the result of an incorrect configuration. For example, if the MicroKernel is unavailable because of configuration settings and the file to be opened is local, then the MicroKernel router returns this status code. 3002: The MicroKernel router resource DLL is unavailable The MicroKernel resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run. Check the Pervasive Event Log (PVSW.LOG) for more information. 3003: The MicroKernel router detected an incompatible network component The networking services component is not compatible with this version of the MicroKernel router. The most likely cause is that the Networking services DLL has been replaced by an older version. Check the Pervasive Event Log (PVSW.LOG) for more information. 3004: The MicroKernel is not responding to the MicroKernel router The MicroKernel is not responding to requests from the MicroKernel router. Verify that the MicroKernel is running. 3005: The MicroKernel router encountered an operating system error The MicroKernel router encountered an unexpected error from the operating system, such as a shared memory failure.
    [Show full text]
  • What's New in Pervasive PSQL Is Divided Into the Following Sections
    Pervasive PSQL v10.10 What’s New in Pervasive PSQL An Overview of New Features and Changed Behavior Pervasive Software Inc. 12365 Riata Trace Parkway Building B Austin, TX 78727 USA Telephone: 512 231 6000 or 800 287 4383 Fax: 512 231 6010 Email: [email protected] Web: http://www.pervasive.com disclaimer PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS IS” BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. trademarks Btrieve, Client/Server in a Box, Pervasive, Pervasive Software, and the Pervasive Software logo are registered trademarks of Pervasive Software Inc. Built on Pervasive Software, DataExchange, MicroKernel Database Engine, MicroKernel Database Architecture, Pervasive.SQL, Pervasive PSQL, Solution Network, Ultralight, and ZDBA are trademarks of Pervasive Software Inc. Microsoft, MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows Millennium, Windows 2000, Windows XP, Win32, Win32s, and Visual Basic are registered trademarks of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are trademarks of Novell, Inc. Sun, Sun Microsystems, Java, all trademarks and logos that contain Sun, Solaris, or Java, are trademarks or registered trademarks of Sun Microsystems.
    [Show full text]
  • What's New in Pervasive PSQL Is Divided Into the Following Sections
    Pervasive PSQL v10 SP2 What’s New in Pervasive PSQL An Overview of New Features and Changed Behavior Pervasive Software Inc. 12365 Riata Trace Parkway Building B Austin, TX 78727 USA Telephone: 512 231 6000 or 800 287 4383 Fax: 512 231 6010 Email: [email protected] Web: http://www.pervasive.com disclaimer PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS IS” BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. trademarks Btrieve, Client/Server in a Box, Pervasive, Pervasive Software, and the Pervasive Software logo are registered trademarks of Pervasive Software Inc. Built on Pervasive Software, DataExchange, MicroKernel Database Engine, MicroKernel Database Architecture, Pervasive.SQL, Pervasive PSQL, Solution Network, Ultralight, and ZDBA are trademarks of Pervasive Software Inc. Microsoft, MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows Millennium, Windows 2000, Windows XP, Win32, Win32s, and Visual Basic are registered trademarks of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are trademarks of Novell, Inc. Sun, Sun Microsystems, Java, all trademarks and logos that contain Sun, Solaris, or Java, are trademarks or registered trademarks of Sun Microsystems.
    [Show full text]
  • Actian Hybrid Data Conference 2018 London Actian Hybrid Data Conference 2018 London
    Actian Hybrid Data Conference 2018 London Actian Hybrid Data Conference 2018 London Turbocharge Your Zen and PSQL Performance Bill Bach President, Goldstar Software Inc. Actian Zen Background What is Actian Zen? Actian Zen, formerly known as Actian PSQL, formerly known as Pervasive PSQL, formerly known as Pervasive.SQL, formerly known as Btrieve: • Stores data for a wide variety of software solutions, in every vertical market imaginable • Offers high speed, low overhead, database access to applications • Provides both transactional (NoSQL) and relational (SQL) access models, giving developers the right tool for the job • Requires no DBA to configure or manage, reducing operational costs 4 © 2018 Actian Corporation What About Previous Versions? Zen has a VERY long history. Here are some previous versions: • Pervasive.SQL 2000i: End of Support: July 1, 2004 • Pervasive.SQL V8: End of Support December 31, 2006 • Pervasive PSQL v9: End of Support: January 1, 2010 • Pervasive PSQL Summit v10: End of Support: March 1, 2012 • Actian PSQL v11: End of Support: July 1, 2016 • Actian PSQL v12: Supported Through July 1, 2019 • Actian Zen v13: Current product, Released June 2017! 5 © 2018 Actian Corporation Benefits of Zen v13 Most Compelling New Features in v13 for End Users: • PSQL Reporting Engine: Offloads SQL workload from main database server, providing horizontal scalability • New Cache Management Functions: Pre-loads (or purges) cache blocks, optimizing engine performance after a restart • Active Directory Security Integration: Simplifies SQL security by leveraging AD groups, simplifying implementation further 6 © 2018 Actian Corporation Benefits of Zen v13 Most Compelling New Features in v13 for Developers: • New SDK’s and API’s: Simplifies development learning curve and provides access from scripting languages (e.g.
    [Show full text]