Show this document in Library frames.
If you don't find the information you seek, please let us know at info@pervasive.com.
If you would prefer to view and read the collateral in a language other than English, please be sure to select the appropriate language from the search selector below.
Please choose any of the following to search documents.

With Pervasive.SQL V8, you can quickly and easily integrate data with with Microsoft Visual Studio.NET development tools and .NET platform services. This paper demonstrates step-by-step how to integrate Pervasive.SQL v8 data in a simple data browser application using the Pervasive.SQL V8 OLE DB Provider, and how to run that application as a web form and Windows form under ASP.NET.
Embedding the Pervasive.SQL engine with an application is a natural step in the evolution of an application. The Pervasive.SQL engine is the choice of many developers for its ease of use, low total cost of ownership, stability and reliability. Developers of applications have several choices for embedding and deploying Pervasive.SQL within their applications. Each method they may choose has benefits and costs in the granularity of control for the chosen deployment method. This paper is focused on discussing the various methods for embedding and deploying Pervasive.SQL.
This Guide to Embedding is a tool to help you decide the best way to embed Pervasive.SQL into your application, and then to provide you the resources to complete the technical parts of your chosen method.
Pervasive.SQL has earned a reputation as one of the fastest database engines on the planet. Pervasive.SQL V8 raises the stakes with an especially strong focus on performance across all data access APIs - without application or deployment changes. This paper explores several major performance related features introduced in Pervasive.SQL V8.
Pervasive.SQL V8 contains two methods of identifying a column of data as a NULL value. The legacy type of Null value is well documented and has been used in Btrieve for years, but the new type of Null identification (True Nulls) as it is used in Btrieve may not be fully understood by everyone. This paper will describe how to use True Null values in Btrieve.
This paper provides suggestions and tips on how to obtain optimal performance when using relational (SQL) access with Pervasive.SQL. To get the most out of relational performance, many things must be considered from database design through application development and deployment. We will discuss in detail the many things that play a role in overall SQL performance using Pervasive.SQL.
A server cluster is a group of independent servers working collectively as a single system to provide high-availability, scalability, and manageability of resources and applications. This paper details Pervasive.SQL support for Microsoft Cluster Service and NetWare Cluster Services. This topic is now covered in the Advanced Operations Guide.
Whether you have either heard about the benefits of fully enabling Pervasive PSQL access in your application, or your customers have asked you for it, you have an existing body of code that represents years of work and customer feedback, and you don't want to rewrite that code in order to take advantage of additional features. This paper explains how to take advantage of the full feature set of Pervasive PSQL while protecting your investment in your application.
Designed as a thin wrapper for the Btrieve API for use in Microsoft Visual Basic, the Pervasive ActiveX Controls are a high-performance, easy-to-use set of tools for rapidly developing database applications in any programming language or development environment that supports ActiveX (OCX) controls. This paper reviews use of the ActiveX controls and provides sample code for implementation.
The Advanced Guide for using ADO and Pervasive.SQL 2000i.
This document provides a high-level overview of Pervasive.SQL 2000 on the Linux platform.
.NET Data Providers for Pervasive.SQL Pervasive.SQL V8 provides full support for the Microsoft .Net framework. Connectivity options include managed ADO.NET, bridging mechanisms as well as transactional access support. This paper reviews and contrasts the various ways that you can use Pervasive.SQL in a .Net environment.
Pervasive PSQL offers a unique combination of transactional and SQL data access that provides COBOL developers the tools to increase the security and flexibility of their application without the risk involved in a major rewrite or the performance drop associated with relational access. This paper is for developers who want to upgrade their data management technology to Pervasive PSQL. It compares Pervasive PSQL to a typical COBOL ISAM database, including steps required to migrate a COBOL application to PSQL and how to overcome obstacles related to more complex data patterns. This paper also describes steps required to ensure that the application continues to perform optimally once the migration has been completed.
What to know what version of the Pervasive PSQL Client is compatible with a particular version of Pervasive PSQL Server? then this is the matrix for you. This matrix covers the various access methods and their compatibility with all Pervasive PSQL versions.

AuditMaster is Pervasive's new transaction intelligence and database monitoring product. This paper describes the technology of AuditMaster

DataExchange is Pervasive's database replication product. It comes in two editions, Real-Time Backup and Data Synchronization. This paper describes DataExchange's core technology, as well as presents the technical differences between the two editions.
This paper explores the different deployment strategies for DataExchange. It includes discussion of one-way and two-way replication and different replication topologies.

The Database Migration Guide is directed towards technical managers and engineers planning a database migration and considering Pervasive.SQL™ as the target data management technology. In this Guide we will review Migrating Data Stores, Schema and Data Definitions, Normalization and much more. We will also review the best way to leverage toe available Data Access Methods available in Pervasive.SQL to both speed up migration while enhancing you applications capabilities.
Until a few years ago, developing with Borland Delphi required using either the Borland Database Engine and an ODBC driver or Titan to access Pervasive.SQL data. With the Pervasive Direct Access Controls (PDAC) , developers have another, better option. Using the PDAC controls, Delphi and C++ Builder developers can access all of the data-aware controls while taking advantage of optimized data access controls. This paper provides an overview of how to approach, implement and deploy PDAC applications.

What happens in the Pervasive.SQL 2000 engine when an application inserts, updates, or deletes a record? The application may be using the Btrieve API, ODBC, Java, or any other interface, but ultimately the insert, update, or delete request gets to the MicroKernel Database Engine (MKDE), which is responsible for getting that change into the physical Btrieve file on the disk. This paper explores MKDE internals, the parameters that control it and optimization techniques.
The MicroKernel Database Engine (MKDE) is the high-performance heart of Pervasive.SQL and includes a tracing function designed to facilitate troubleshooting issues across any of the Pervasive.SQL data access methods. This trace function captures all of the interaction between the application and the database engine. This resulting trace file can be used to follow the operations originating with any access method to the Pervasive.SQL engine. Either from your application or from third party tools. This paper describes the functionality of the MKDE.TRA file, how it is created, and how to interpret the information.

Backup Agent manages Pervasive.SQL's continuous operations feature to ensure that the data files of an operating database are clean and consistent for reliable backup to tape, disk, or other media.

Organizations increasingly wrestle with the need to build sophisticated data pipelines to quickly and efficiently handle data feeds coming from customers and going to customers, suppliers, and trading partners. They most often require an integration platform that will allow them to quickly and efficiently convert pertinent information from customer data feeds. However, to ensure success, major concerns must be addressed in building, maintaining, and leveraging customer data feeds that revolve around data demands, mapping needs, communication protocols, and reformatting for business partners.
Users of Pervasive Data Integrator and Pervasive Business Integrator will benefit from understanding the design-time and run-time aspects of the technology behind these products. Pervasive integration products are built upon a common integration architecture that enables ETL, EII, EAI and SOA deployment models. The white paper discusses how this common architecture brings together the best in productivity tools for maximizing developer efficiency, project scalability, and ease of project management with open repositories to house large-scale, organic integration designs.
In this paper, Yankee reveals groundbreaking research on the insidious costs in the integration lifecycle and explores strategies for IT executives to assess and reduce the total cost of data, application and business integration based on more than 400 implementations of data and application suites from enterprises using products from more than 20 vendors.
Oracle Integration projects need to accommodate a high level of variety and change involving a large number of systems, applications, data formats, standards, and connectivity types - all existing in a perpetual whirl of change for both legacy systems, unstructured data sources, and new applications. Driven by business and technical factors, this growing volatility makes the goal of establishing a workable and maintainable SOA infrastructure hard to achieve. A new mechanism for managing the “last mile” adaptation problem is needed.
For Service Oriented Architecture projects to be successful, they must accommodate a high level of variety and change. Using Composite Adapter Services as the key building blocks of a flexible integration strategy, SOA can accommodate variety and change, and deliver on the promises of the agile enterprise. Composite Adapter Services provide a layer of abstraction between Service Requestors and Service Providers, enabling enterprise integration that is cost-effective, loosely coupled, extensible, and can bridge the new world of SOA with the old world of IT infrastructure built over the last 30 years.
The application software market is mature and most of the business applications that an organization needs are already deployed. The major area from which business benefit will now come is through building on this foundation and the major requirement for most IT organizations now is integration.
The challenges that face organizations are ever evolving and today’s business climate is no exception. Many of yesterday’s challenges have been met and now organizations face new hurdles in an effort to improve margins, increase revenues per customer and grow market share. Among the latest generation of challenges is integration of business processes, applications and systems across the extended enterprise, which includes employees, customers, partners and suppliers. IT departments must be able to respond to current and future business demands. They need to leverage current investments in infrastructure, applications, people and processes, as well as identify new business opportunities. This requires data access anywhere, at anytime, on any device, across organizational boundaries in order to create a value proposition that drives sales and revenues across the entire customer base. Needless to say, this is a daunting task.
Successful integration for today's business must accommodate a high level of variety and change involving a large number of systems, applications, data formats, standards, and connectivity types—all existing in a perpetual whirl of change for both legacy systems and new applications. Driven by business and technical factors, this growing volatility makes the goal of enterprise integration a complex, hard-to-reach moving target for today's IT professionals.
An organization that wishes to integrate disparate computing resources can either build an integration solution in-house or buy a packaged integration software application. While building a custom application may seem the most cost-effective route, this approach is fraught with problems. Gartner Group estimates about 30% of the cost of an ERP project arises from the need to build integration links with existing applications. Packaged integration software applications now offer a compelling alternative to the expensive, time-consuming quagmire of in-house development.
Today’s mid-size organizations have disparate applications and require software integration functionality similar to much larger enterprises. However, traditional approaches to integration are prohibitive for smaller businesses due to development and maintenance costs associated with labor. By choosing packaged solutions, mid-size companies can experience all of the benefi ts of data and business integration and dramatically minimize costs.
This guide describes the unique Pervasive integration architecture and is designed to facilitate a thorough, easy-to-follow evaluation of Pervasive’s integration product set, providing a clear understanding of its real-world applications through product tutorials and various integration project scenarios. Test-drive these tutorials today to empower your organization with a flexible, reusable, cost-effective integration solution that will accommodate your frequently changing business needs and requirements.
HIPAA transactions and HIPAA privacy requirements are generating the need for a higher level of integration than ever before.
Get a fresh perspective on Web services with this thought piece.