|
Before you begin, you should understand some basics about Pervasive database engines. The Pervasive.SQL engine consists of two kinds of access layers-transactional and relational. Combining these two forms of access delivers powerful benefits-the performance of transactional data access integrated with the robustness of relational data. The engine operates as stand-alone engine or as a client/server engine. In standalone environments, the engine resides on the same machine as the application and data. In client/server environments, the engine and data reside on a network server and the application resides on a client machine.
In order for the client application to communicate with the server engine and connect to the database, the client application must use a requester. (In standalone environments, a requester is not necessary.)
For more information about standalone and client/server configurations, refer to Pervasive Products and Services. For a glossary of Pervasive terms, refer to the Online Glossary, which is accessible from the Pervasive.SQL documentation help file on the Start Menu.
|
Chapter contents
Prev topic: Introduction to Pervasive Samples
|