banner



How To View Current Downloads Windows 7

Btrieve is a transactional database (navigational database) software product. It is based on Indexed Sequential Access Method (ISAM), which is a fashion of storing data for fast retrieval. There take been several versions of the product for DOS, Linux, older versions of Microsoft Windows, 32-flake IBM OS/two and for Novell NetWare.

Information technology was originally a record director published by SoftCraft. Btrieve was written by Doug Woodward and Nancy Woodward and initial funding was provided in function by Doug's blood brother Loyd Woodward. Around the same time as the release of the first IBM PCs, Doug received 50% of the company as a wedding gift and afterward purchased the rest from his brother. Subsequently gaining market share and popularity, it was acquired from Doug and Nancy Woodward by Novell in 1987, for integration into their NetWare operating organisation in addition to continuing with the DOS version. The production gained significant market place share as a database embedded in mid-market applications in addition to being embedded in every copy of NetWare two.x, 3.x and iv.ten since information technology was available on every NetWare network. After some reorganization within Novell, it was decided in 1994 to spin off the production and technology to Doug and Nancy Woodward along with Ron Harris, to be developed by a new company known as Btrieve Technologies, Inc. (BTI).

Btrieve was modularized starting with version 6.15 and became ane of 2 database front-ends that plugged into a standard software interface called the MicroKernel Database Engine. The Btrieve front end-end supported the Btrieve API and the other front-end was called Scalable SQL, a relational database product based upon the MKDE that used its ain diverseness of Structured Query Language, otherwise known equally SQL. After these versions were released (Btrieve half-dozen.15 and ScalableSQL v4) the company was renamed to Pervasive Software prior to their IPO. Shortly thereafter the Btrieve and ScalableSQL products were combined into the products sold as Pervasive.SQL or PSQL, and later Actian Zen. Btrieve continued for a few years while ScalableSQL was quickly dropped. Customers were encouraged to upgrade to Pervasive.SQL, which supported both SQL and Btrieve applications.

Architecture [edit]

The MKDE model allows for different database backends to be plugged into Pervasive'south production

Btrieve is not a relational database management organisation (RDBMS). Early on descriptions of Btrieve referred to it every bit a record manager (though Pervasive initially used the term navigational database merely later changed this to transactional database) because it just deals with the underlying record creation, data retrieval, record updating and information deletion primitives. Information technology uses ISAM as its underlying indexing and storage mechanism. A central part of Pervasive's architecture is the use of a MicroKernel Database Engine, which allows unlike database backends to be modularised and integrated hands into their DBMS package, Pervasive.SQL. This has enabled them to support both their Btrieve navigational database engine and an SQL-based engine, Scalable SQL.

Current versions of Btrieve back up system transactions and user transactions, where system transactions are a bundle of non-transactional operations and/or user transactions, whereas user transactions are transactions that piece of work on actual data in the database. Organization transactions were developed to allow multiple transactions to be washed in a batch and to brand data recovery easier.

The Btrieve file format consists entirely of pages, which are the data that motion between retention and storage when the engine performs an input/output performance. Versions prior to 6.0 merely used data pages, alphabetize pages and a file command record. The file had an index for searching that linked to physical pages. Beginning with version half-dozen.0 logical pages were used. Logical are mapped to physical pages (pages at a fixed location in the file) on the deejay by page allocation tables. The file control record contains important information virtually Btrieve files, such as the number of pages in electric current utilise. To avert database abuse, Btrieve uses ii methods of updating records: pre-paradigm paging in Btrieve versions before 6.0, and shadow paging in subsequent versions. It was primarily the change-over from pre-epitome paging to shadow-paging, which necessitated radical file format changes, that acquired compatibility issues between version half dozen and previous versions.

History [edit]

Btrieve has been owned and adult by four different companies: SoftCraft, Novell, Btrieve Technologies, Inc. (later renamed Pervasive Software), and Actian Corporation. They have a committed and loyal developer-base and according to visitor literature, they remain fully committed to the production. Pervasive Software set up up a "Btrieve Society" to recognise existing developers.[ane]

Under DOS, Btrieve up to version 5, was a terminate-and-stay-resident program (TSR) which functioned equally an application programming interface (API) database engine, supplying applications programs with function calls to implement a multi-user database with record locking. The network version worked in a similar way.

In the early years, DOS versions upward to version 5 sold for a price of around U.s.a.$1,000, only the executable TSR database engine file could exist distributed with applications without charge.

SoftCraft years [edit]

The product was launched in February 1982 past SoftCraft, a firm located in Austin, Texas, by Doug and Nancy Woodward. Doug became the vice-president and handled software development, Nancy became the president of the company. They released a number of versions over the side by side few years: in February 1983 they released the Btrieve 2.x series, and when MS-DOS 2.0 adult support for file and directory handles, they released Btrieve 3.0. When MS-DOS 3.one standardised its internal interfaces in March 1985, they released Btrieve 3.1 C/S i month afterward, which had network and customer/server support. In February 1986, Btrieve 4.0 was released, and when the 4.one upgrade was released it gained support for extended key types and supplemental indexes.

Although Btrieve was fairly popular, it was an API database engine. The killer-app database manager on the PC, dBase II and its successors, were database management systems (DBMS) which could be used either as a free-standing, full general-purpose application, or a database programming language. Btrieve was also more expensive to buy than dBase, although run-time licensing was free of charge. Btrieve grew to a developer base of operations of over 5,000 users and was widely used in the fiscal area.[2] The visitor took some time to create a user interface for the product, nevertheless in 1984 they released Xtrieve, a menu-driven plan that used a new .DDF information dictionary to enforce relational database rules.

Novell acquisition [edit]

Novell logo-darkened.png

In 1987, Novell started diversifying and ownership companies to add to their NetWare operating system. Ane of the companies they purchased was SoftCraft. Nancy Woodward became the Vice-President and Full general Manager of Novell'south Austin operations while Doug Woodward became the Vice-President of Advanced Database Technologies. Early the side by side year, Btrieve 5.0 was released to run as a native NetWare application, or Value Added Process. According to Jim Kyle, "it had auto-increase key types, the BROUTER network procedure server, data-but and fundamental-but files, and optional data compression".[2] Version 5.ane was released in 1990 with increased file-handling transaction capability, logging and roll-forward operations, along with several API enhancements. Several versions were created for DOS, Bone/2 and Microsoft Windows. Version six.0 was released in June 1992. However, it was not promoted extensively by Novell, and due to enhancements, (such as the modify from pre-imaging to shadow-paging) it was incompatible with previous versions of Btrieve. The market did not increase much for Btrieve and information technology did not see wide adoption due to these bug.

When the visitor was acquired by Novell, SoftCraft had been working on a product chosen XQL, an SQL interpreter designed to better bargain with industry standard SQL, which the Xtrieve package was not fully compliant with. This became the footing for NetWare SQL, which was initially released in 1989, and was a bare-basic SQL interpreter which implemented the base IBM version of SQL.

Btrieve Technologies, Inc. [edit]

Btrieve logo.PNG

By 1994, Novell had largely given upward on attempting to make NetWare into a complete culling operating system, and started selling off many of the companies it had acquired only a few years earlier. They had minimally promoted Btrieve, largely due to the delay (24 months) in releasing version 6. Negotiations between The Woodwards and Novell were entered into, and later two years Novell announced on 26 Jan, 1994 that it was going to transfer ownership of Btrieve to Btrieve Technologies, Incorporated (also known as BTI). On 29 April 1994, the transfer was completed and Nancy Woodward became the Chairman of BTI and Doug Woodward was made the Main Technical Officer. The CEO position was given to Ron Harris, a onetime employee of Texas Instruments, and one of the founding employees of Citrix Systems, Inc. where he was employed first equally Manager of Strategic Planning, then as Vice-President of Marketing, and finally as the Product Group Vice President.

Btrieve was totally rewritten, and on ane July 1994 Btrieve vi.15 for DOS, Windows and OS/two was released. Novell SQL was renamed to Scalable SQL reflecting the alter in ownership of the visitor. In 1995, version 6.15 was released for Novell NetWare, Windows NT Server and for Windows NT/95, and thus became a cross-platform database product. The concept of a Micro Kernel Database Engine (MKDE) was introduced in this version.

Pervasive Software [edit]

In 1996, the company renamed itself to Pervasive Software, and their product to Pervasive.SQL. In 1997, the company went public. They did this in order to allow greater penetration of the relational database market place and to re-align as an SQL vendor, though they are still marketing and developing Btrieve. Pervasive completed its IPO in September. The visitor continued using the MKDE in version 6.thirty. In 1997, Pervasive released ScalableSQL 4.0, a relational database product, and Btrieve 7.0.

In 2000, Novell was criticized after it ceased bundling Pervasive.SQL with NetWare from version 5.1 onwards; instead, it shipped with a trial version that shut down after 90 days.[3] The latest version, Pervasive PSQL Elevation v11, was released in September 2010.

Actian Corporation [edit]

In 2013, Actian Corporation acquired Pervasive Software.[4] In Feb 2016 Actian released Btrieve 12.

Versions [edit]

Btrieve for DOS [edit]

There was one DOS client-based configuration of Btrieve created by SoftCraft. SoftCraft'due south definition of a customer-based version was a "Btrieve engine running on a particular workstation."[5] This meant the record-management engine connected directly to the files via operating system functions and modified the records appropriately, whether the files were local or on a network. The customer-based engine allowed v concurrent users to admission the database at whatever i fourth dimension. All record processing was done on the workstation the engine was installed on. In later versions, Btrieve for DOS could employ either of 2 modes: what they called SEFS (Single-Engine File Sharing) or MEFS (Multi-Engine File Sharing).

Btrieve for Netware [edit]

Btrieve for Netware was substantially the aforementioned every bit Btrieve for DOS with some extra features available simply on Netware at the fourth dimension. It ran a server procedure, called BSERVER, on the file-sharing server and this managed data input/output in conjunction with the network file organization. The server process was get-go implemented as a Netware Value-Added Process (VAP) chosen BSERVER.VAP, but was switched to a Netware NetWare Loadable Module (NLM) presently afterwards. BSERVER was the database engine that dealt with admission to records, even so information technology also accepted requests for the transmission of requested information to some other server via the BROUTER procedure.

Btrieve used requesters to make database input/output requests from the client workstation. The requesters were available for DOS, Bone/2, Microsoft Windows, and UnixWare. The program BREQUEST.EXE accepted input/output requests via the Btrieve API and relayed them to BSERVER. It then handled the responses from BSERVER and relayed them back to the advisable application.

The BROUTER process immune for incoming requests to be "routed" to a re-create of the database on another server. It was loaded on the Netware server and dealt with advice betwixt multiple server processes running on the file-server through the use of two File Server Tables. According to Pervasive, these provide a listing of "server names and addresses, and the Server Routing Tabular array".[6] BROUTER also enabled communication requests to be routed to the correct server via SPX by looking up the BSPXCOM NetWare Loadable Module and coordinated locks and other mechanisms that controlled admission to the data in the Btrieve database.

Btrieve for DOS used the SEFS and MEFS modes for file sharing, and because information technology was able to run on a network it was able to apply exclusive and concurrent transactions.

Btrieve for Windows [edit]

Btrieve for Windows was created before the company rewrote the codebase to use the MKDE. It featured SEFS and MEFS file sharing mechanisms; used shadow-paging and allowed for exclusive and concurrent locks. It handled version 6.x and 6.1 files differently. Version six.ten files could handle operations on part of a record rather than locking the entire record. It handled records larger than 64KB, implemented VATs, ACSs, new information types, allowed for per centum operations (where the tape could be located and manipulated by the concrete location in the file) and handled indistinguishable keys. Version 6.x was capable of dropping or adding whatsoever alphabetize on the fly (version 6.0 and below could drop simply supplemental indexes). Version 6.1 files allowed for concurrent and system transactions, the optional renumbering of keys, case insensitive ACS tables, and enhanced locking operations.

Btrieve for Windows could run as a customer to the database that utilized SEFS or MEFS modes, or information technology could directly access the Btrieve server.

Client-based Btrieve [edit]

Btrieve for Windows 95NT Workstation config.svg

The client-based version of Btrieve has all the database files either direct on the local calculator or via a mapped network drive (prepare via the DOS Internet USE command).

Applications make a function phone call to WBTRCALL.DLL, a loader and requester interface. The loader and requester module verify the BTI.INI configuration file is correctly set up to load the client-based Btrieve engine. In turn, this loads the local interface to the btrieve engine (WBTRLOCL.DLL). If necessary, this local interface loads the Btrieve engine (WBTR32.EXE) into retentivity and sends the necessary database requests to it. The database engine and so calls various Win32 system libraries to perform file operations on the database files.[seven]

Customer-based Btrieve accessing server-based Btrieve [edit]

The client-based version of Btrieve for Windows could admission server-based versions of Btrieve via a DOS-based "requester". The requestor required the use of DOS Protected Mode Interface (DPMI) which immune programme admission to DOS extended memory accessible only via the CPU's Protected Style.

As with the client-based interface, the Btrieve-based application makes a call to the WBTRCALL.DLL loader and requester interface library. This library checks the BTI.INI file to see if it needs to admission data on the local organization or whether it needs to access data on a remote server. If it needs to access the server, and then information technology uses the Windows version of DPMI to access a DOS-based requester named BREQUEST.EXE. The requester then establishes a network connexion to the server, which processes the request and passes back a message to the requester when the database request is completed.

Btrieve for Windows NT/Windows 95 [edit]

Btrieve for Windows NT and Windows 95 was released in 1995, along with Btrieve for Netware and Btrieve for Windows NT Server. Information technology had reached version 6.15 and started using the MKDE. The file sharing mechanisms remained the same, as it still used SEFS and MEFS file sharing modes, shadow-paging and allowed for exclusive and concurrent locks. This version of Btrieve allowed for aught values in keys, which meant that a record could be entered into the database when information on the key was not bachelor. It meant the key would not be included into the alphabetize, and this helped subtract unnecessary searching of the database via the alphabetize. Information technology also introduced the concept of a system transaction and a user transaction. (see System and user transactions). The MKDE also allowed gaps between auto-incremented keys. Variable-tail allotment tables were introduced in version 6.15, and then they were included in the Windows NT/95 build of Btrieve.

There are ii configurations of Btrieve for Windows NT/95, standalone workstation and client/server.

Standalone workstation [edit]

Btrieve for Windows 95NT Workstation config.svg

When using the standalone workstation configuration of Btrieve, all processing of records is washed on the local workstation. The workstation relies on the underlying mechanisms of Windows to allow the MKDE (programme W32MKDE.EXE) to gain straight access to the database files, and uses lock files to bargain with concurrency issues.

In this configuration, the application makes calls to the Btrieve API, or Microkernel Interface (WBTRV32.DLL). The phone call is then candy by the interface and passed to the MKDE (W32MKDE.EXE) which uses the underlying operating system file system (whether it be network or local) to directly admission the database files.[8]

This leads to some peculiar issues. If Btrieve uses Windows file sharing and has the database engine open files directly on a file share, for instance, and in that location is network instability (e.g. a network cable is asunder) during an update the fields used to link ane Btrieve file to another can become unsynchronized (to all intents and purposes the data loses its relationships or links to other data) and the database file itself tin go corrupted (though the chance of this is reduced due to pre-paradigm paging).

Client/Server [edit]

MKDE server.svg

When using the client/server (or Server edition) configuration of Btrieve, processing of records is generally done on a Windows file server via a mapped drive (a style of mapping a file share to a "virtual" disk drive in Windows via the Cyberspace Apply command). It utilises the permissions that y'all are assigned when authenticating, either log-on permissions, or permissions given when Cyberspace Use is utilized.[ix]

On Windows 95, the MKDE interface (a Windows dynamic link library (DLL) called WBTRV32.DLL) determines what database access method is in utilize via the configuration file. If it detects both the client/server and workstation engines are installed on the aforementioned machine, it checks whether the target is gear up to workstation or server. If running on Windows NT and the server procedure NTMKDE.EXE is running along with the standalone workstation process W32MKDE.EXE it looks in the registry to determine if the target is a server or workstation. In both cases, if the MKDE interface is set to workstation, (the "Standalone workstation" configuration) it uses the MKDE (W32MKDE.EXE) to access the file straight. If it is set to server, the MKDE interface on the client uses a communications module (on Windows 95 this is W32BTICM.DLL, on Windows NT this is NTBTICM.DLL) that "talks" to the server. The server itself has its own matching communications module (over again either W32BTICM.DLL or NTBTICM.DLL) that resides on the mapped drive. The server DLL communicates with the server MKDE (NTMKDE.EXE) which updates records, and then sends a confirmation that the operation succeeded, back through the communications module to the client.[10]

The advantage of this system is, if a network connection failure occurs, the MKDE on the server will exist able to observe it and recover in a more graceful manner than the workstation configuration is able to.

Configuration [edit]

A configuration utility was included with Btrieve to alter MKDE settings. The settings that could exist inverse were:

  • File settings: this category contains settings related to files, file handles, record locks, indexes, and log files. The number of open files and logical file handles was set up in here, every bit well every bit the number of record locks per client; alphabetize balancing and an pick to create files in pre 6.x format are in this category. It also controlled whether the Microkernel kept a log of operations executed on selected files. In this section the method of file sharing could exist set to either MEFS or SEFS. The organization transaction concord limit sets the number of system transactions performed during write operations for shared files.
  • Retentiveness organisation: this category contained settings related to the size of buffers the Microkernel needed to classify for various purposes.
  • Client/System transactions: this category contains settings related to transactions, including the number supported and how and when they volition exist logged.
  • System resources/directories: this category contains settings related to the number of clients and threads supported as well as the location of diverse system files.
  • Trace operations: this category contains settings related to tracing diverse Btrieve operations. Tracing is an avant-garde feature used mainly for debugging purposes.

Pervasive.SQL 7 [edit]

Pervasive.SQL 7 was released in March, 1998, and included Scalable SQL four and Btrieve seven.0. Btrieve 7.0 ran on the same platforms equally Btrieve half-dozen.10: Windows 95, Windows NT iii.51 & 4, Netware and DOS. However, the company changed to a component-based architecture called SmartComponents to resolve compatibility issues with upgrades. This used a component identification scheme both embedded into the file and encoded into the file name, along with dynamic bounden of "glue files" (DLLs loaded into memory only when needed). The dynamic binding of components was done using a new "Abstract OS Services DLL" that looked for the latest version of the appropriate needed component via the file proper noun encoding. This "glue module" is then loaded into memory and used.[11] The old log file format of Btrieve 6.ten was also replaced with a new centralised log chosen PVSW.LOG and that had a unified and enhanced log file format. They likewise improved their mistake messages and fault message reporting mechanisms.

The MKDE was retained in Pervasive.SQL 7. However, due to the new component architecture's dynamic binding, the internal compages was modified. The application using Btrieve calls a services managing director which then searches through various configured directories for specific encoded filename. The file name loaded for Btrieve files in Backus–Naur form is:

                        <            filename            >            ::=            <            platform-code            >            "BIF"            <            major-functional-level            >            <            minor-functional-level            >            <            platform-lawmaking            >            ::=            "W1" | "W2" | "W3" | "W9" | "WT" | "NW" | "O3"            <            major-functional-level            >            ::=            <            number            >            <            minor-functional-level            >            ::=            <            number            >            <            number            >            <            number            >            ::=            "0" | "ane" | "2" | "three" | "4" | "5" | "vi" | "7" | "eight" | "ix"          
Embedded filename platform codes
Code Platform
W1 Windows three.1x, incl. Windows for Workgroups (Win16)
W2 Extended Windows (32-fleck Watcom Extender)
W3 Windows 95, Windows NT (Win32)
W9 Windows 95
WT Windows NT
NW NetWare 3.x and iv.x
O3 OS/2 (32-bit)

The "glue" module, which is a DLL, is loaded into memory and becomes the interface to the MKDE. The MKDE then determines whether it is configured to be a workstation-based configuration or a server-based configuration. It and then passes requests via its communications "requester" module onto the database server, or direct modifies the database files if configured in workstation fashion.

Pervasive.SQL 2000/2000i [edit]

Pervasive.SQL 2000 and Pervasive.SQL 2000i use essentially the aforementioned architecture as Pervasive.SQL 7, though 2000i includes i*Net server. It uses the same component model, has the ability to apply the Btrieve or Scalable SQL engines and continues using an MKDE. This version included support for Cherry-red Chapeau Linux, Caldera OpenLinux, SUSE and Solaris. It also had amend integration with Last Services, though simply one instance of the database engine may run on whatsoever terminal server platform. Y'all cannot run separate copies of the database engine within two or more than terminal sessions.

Pervasive.SQL V8 [edit]

Introduced in December 2002, Pervasive.SQL V8 improves the performance of both Btrieve and SQL applications using a number of new technologies.

  • Customer side caching greatly improves read operation past maintaining a portion of the database's contents on the local PC.
  • Turbo Write Acceleration (TWA) groups deejay writes into groups, minimizing interactions with disk.
  • Transaction Logging provides a slightly less failure protection than transaction durability, but improves overall performance.

The V8 Security Characteristic Pack (a mid-release product update designated 8.5) added important new security features designed to lock down Pervasive.SQL data files. Prior to 8.v, access to Btrieve data was controlled by the operating system's security mechanism. This meant that any user who needed read/write admission to the database, also needed read/write admission to the underlying data files. 8.five introduced new security models, which allow administrators to command access to the Btrieve data using database security. Once activated, database security no longer requires that the user has access to the underlying files. In addition, client/server configurations no longer crave the use of network shares or mapped drives. Applications tin can reference secure Btrieve data using a URI connection string.

Pervasive PSQL v9 [edit]

Pervasive PSQL v9 includes new Java GUIs, built on the Eclipse framework. These GUIs are available for both Microsoft Windows and Linux. In addition, v9 included many SQL performance and syntax updates, improving both the speed and flexibility of all of the SQL interfaces - ADO.Net, JDBC, ODBC, and OLE DB. Finally, PSQL v9 expanded the Btrieve maximum file size from 64GB in eight.ten and earlier file formats to 128 GB in 9.0 format files, and again to 256GB for files in the ix.v file format.

In conjunction with PSQL v9 Pervasive reintroduced the DDF Builder utility and added support for text searching with the Total Text Search (FTS) add-on, which was later removed from the product line. DDF Builder provides a mechanism for Btrieve users to define the meta information for existing Btrieve files, thus allowing Btrieve data to be accessible via SQL tools and utilities.

All versions of the MKDE retain full astern read-level compatibility with before versions of Btrieve, including those that pre-date introduction of the MKDE itself, and practice not modify the file's version unless specifically requested to practice so. Btrieve files that are in the 5.x or older file formats MUST exist rebuilt (using the GUI or command line Rebuild utilities) to 6.10 or newer format to support database writes from the 9.0 or newer database engine.

Pervasive PSQL v10 [edit]

Pervasive PSQL v10 was released in September 2007 and was the first version of Pervasive PSQL Server and Client to provide support for 64-bit operating systems. The Btrieve API and distributing tuning interface (DTI) were both enhanced to support 64-bit. Pervasive PSQL Workgroup and other components of the SDK were not enhanced for 64-bit support.[12]

The release of Pervasive PSQL v10 was timed to offering support for the and so newly bachelor Windows Vista and soon to arrive Windows Server 2008 operating systems. Pervasive PSQL v10 Server, Workgroup and Client all support Windows Vista. Pervasive PSQL v10 Server is Certified for Windows Server 2008.

Also included in Pervasive PSQL v10 was Xtreme input/output (XIO), a 32-flake Windows database accelerator that enabled access of extended retentivity to aggrandize the database buried past the normal 2GB limit on 32-scrap Windows systems. Xtreme input/output as well included update pinch algorithms and streamlined writing techniques to better database input/output performance.[13]

Digital license enforcement, called Product Dominance, was introduced for the Pervasive PSQL production line with Pervasive PSQL v10. Product Authorization was initially implemented with trial downloads and e-commerce orders. Products sold through the Pervasive Distributor and ISV partners were upgrade to include product authorization with the release of Pervasive PSQL v10 SP3 in November 2009. Pervasive PSQL v10 SP3 was also released as a Windows 7 compatible application.

Pervasive PSQL v10 retained backward compatibility by using the nine.5 file format with an increase in the maximum data file size to 256GB and increase in the maximum page size to xvi,384 bytes.

Support for NetWare, Windows NT, Windows 98, Windows ME, DOS 6.22 and 16-bit applications were dropped with Pervasive PSQL v10. Although the Windows and Linux versions of Pervasive PSQL v9 products are no longer sold, Pervasive notwithstanding sells and supports Pervasive PSQL v9 for NetWare.

In 2010, Pervasive Software released Pervasive PSQL v11, which allows users to take total reward of multithreading for faster database processing.

Pervasive PSQL v11 [edit]

Pervasive PSQL v11 was released in September 2010. One of the primal drivers of the engineering effort behind Pervasive PSQL v11 was the redesign of the database engine to increase performance and scalability on multi-core CPU'south. Pervasive PSQL v11 optimizes parallel threads performing similar activities, allowing the database to engage multiple cores during task execution. PSQL v11 too provides enhancements to the depression-level synchronization mechanisms in the navigational interface. Multiple users can read the same cached file pages simultaneously and their operations can proceed on independent cores. Non-user activeness such as checkpoints and log direction tin run on separate cores and multiple users accessing independent files can proceed on different cores.[14]

Multi-core support is available with all versions of PSQL v11: 32- and 64-bit Windows and Linux Servers, and 32-scrap Workgroup. Internal testing at Pervasive documented performance increases of 300% when comparing PSQL v10 to PSQL v11 on an 8-core server running Microsoft 2008 Enterprise Server SP2(64-bit).[15]

(IPv6) support on Windows is included in Pervasive PSQL v11 with connected support for IPv4 environments. Pervasive PSQL v11 supports IPv6 with both the Btrieve and DTI (Distributed Tuning Interface) access methods.

64-chip server versions of PSQL v11 include a 64-bit relational/SQL engine likewise as the 64-flake navigational/Btrieve engine, forth with a 64-fleck ODBC driver. The driver is installed with the 64-bit versions of PSQL Server and PSQL Client.

Pervasive updated the PSQL software development kit with the improver of the Pervasive PSQL ADO.Internet Data Provider iii.5. The Information Provider 3.5 is compliant with .Net Framework versions 2.0, three.0, 3.5, 3.5 SP1 and 4.0, and runs under .NET Framework 4.0 with support for Entity Framework ane.0 features.[fourteen] Pervasive PSQL v11 also updated the PDAC (Pervasive Direct Access Components) admission method with back up for Embardacero's RAD Studio 2009 and RAD Studio 2010.

Product Authorization was extended in Pervasive PSQL v11 to include OEM customers, along with the introduction of a web-based portal for OEM'south to generate keys and manage licenses for PSQL v11. Telephone authority (a method of authorizing Pervasive PSQL without requiring an Internet connection) was first introduced with PSQL v11 and made available to all Pervasive customers.

Pervasive PSQL v11 continues with the 9.five file format, maintaining backward compatibility with previous releases.

Back up for Windows 2000 was dropped with Pervasive PSQL v11.

Pervasive PSQL Ecosystem [edit]

Pervasive now offers a number of improver products which extend the basic features of the PSQL DBMS. The latest versions of each of the products, AuditMaster v7, Backup Agent v3, and DataExchange v4, were released in Dec 2010.

  • Pervasive AuditMaster provides existent-fourth dimension auditing of all database interactions, whether Btrieve or SQL. Logs of data events can be queried to rails changes to sensitive information. Alerts can besides be created to notify the appropriate personnel or launch the associated process.
  • Pervasive Backup Agent manages PSQL's continuous operations mode and allows backup software to reliably re-create online databases.
  • Pervasive DataExchange provides data synchronization and replication between two or more PSQL engines, ensuring that critical data is always bachelor.

Btrieve 12 [edit]

In February 2016 Actian appear Btrieve 12.[16] Actian say Btrieve 12 has new features, is compatible with Microsoft Windows Vista to ten, and Windows Server 2008 and 2012, and is file format and API compatible with Btrieve half dozen.15, allowing it to read and write Btrieve 6.15 files from before 16-bit and DOS applications.[17]

See likewise [edit]

  • Architecture of Btrieve
  • Admission Database Engine (ACE and formerly JET)

Notes [edit]

  1. ^ "Archived copy". Archived from the original on 2004-12-11. Retrieved 2004-12-22 . {{cite web}}: CS1 maint: archived re-create equally title (link)
  2. ^ a b Kyle, Jim (1995). Btrieve complete: a guide for developers and systems administrators. Reading, Massachusetts: Addison-Wesley Publishing Company. p. 7. ISBN0-201-48326-ii.
  3. ^ Foster, Ed (2000). "Hear the sucking sound? That Novell upgrade may cost more than than expected". Infoworld. Archived from the original on 2004-11-30. Retrieved 2004-12-12 .
  4. ^ "Actian Corporation and Pervasive Software Unite to Take Action on Big Information".
  5. ^ Pervasive (1997). Btrieve for DOS Installation and Functioning manual (PDF). p. 1. Archived from the original (PDF) on 2004-06-19.
  6. ^ Pervasive (1998). "Status 96 from a NetWare Loadable Module Awarding (article ID: BTRTT-97070801)". Pervasive KnowledgeBase. Archived from the original on 2004-10-27. Retrieved 2004-12-12 .
  7. ^ Pervasive (Nov 1996). Btrieve for Windows Installation and Operation (PDF). pp. 2–five, 2–6. Archived from the original (PDF) on 2005-x-02. Retrieved 2004-12-23 .
  8. ^ Pervasive (Nov 1996). Btrieve for Windows NT/Windows 95 Installation and Operation (PDF). pp. 2–3. Archived from the original (PDF) on 2008-07-04.
  9. ^ Btrieve for Windows 95/NT Installation and Operation, 2–v
  10. ^ Btrieve for Windows 95/NT Installation and Operation, 2–4
  11. ^ Pervasive (Feb 1998). Pervasive.SQL 7 User'south Guide (PDF). pp. 22–28. [ permanent dead link ]
  12. ^ Pervasive (2007). "What was New in Pervasive PSQL v10". Pervasive Documentation . Retrieved 2010-07-xxx .
  13. ^ Pervasive (March 1998). Pervasive PSQL Xtreme I/O: Delivering Performance for 32-bit Applications (PDF). pp. 3–five. Archived from the original (PDF) on 2007-ten-21.
  14. ^ a b Pervasive (2010). "What's New in Pervasive PSQL v11" (PDF). Pervasive Documentation . Retrieved 2010-09-30 .
  15. ^ Pervasive (2010). "Benchmark Performance Results for Pervasive PSQL v11" (PDF). Pervasive Documentation . Retrieved 2010-09-29 .
  16. ^ "Actian Releases Btrieve 12 to Enable Existing Users to Move to Newest Os and Hardware Platforms". Actian.com. eight February 2016. Retrieved 2 March 2016.
  17. ^ "Btrieve 12 - Actian – Accept Activity on Big Data". Actian.com . Retrieved 2 March 2016.

Sources [edit]

  • Trocino, Richard B. (1994). The Illustrated Guide to NetWare Btrieve 6.10. Gold Due west Products International. pp. 19–24.
  • Novell. Components of NetWare Btrieve. Retrieved December 12, 2004.
  • Pervasive (2004). Btrieve past, present and futurity: Remember when Btrieve rocked the database world?. Company history webpage.
  • Pervasive (March 2001). Pervasive.SQL 2000i: Getting Started (Server Edition). Product manual.

External links [edit]

  • Pervasive Software Inc. — makers of Btrieve and PSQL
  • Btrieve Society
  • comp.databases.btrieve — Btrieve newsgroup
  • Pervasive Software online manuals

Source: https://en.wikipedia.org/wiki/Btrieve

Posted by: rankintwen1982.blogspot.com

0 Response to "How To View Current Downloads Windows 7"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel