Relational Architectural Overview

---

The following diagram illustrates the architectural components of Pervasive.SQL's relational ODBC interface for the server version. The SQL Connection Manager starts and runs as a service on Windows NT (W3SQLMGR.EXE), as an NLM on NetWare, and as a daemon on Unix.

Pervasive.SQL Relational Architecture: Server

On Windows, the SQL Connection Manager consists of one executable and three DLL files:

• W3SQLMGR.EXE - SQL Connection Manager
• W3MGRMSG.DLL - Message File
• W3MGRRES.DLL - Resource DLL
• W3MGRRSX.DLL

The SQL Connection Manager supports up to 2000 simultaneous connections and uses the ODBC Driver Manager to make calls to the SQL Relational Database Engine (SRDE), which in turn rests on top of the MicroKernel.

Figure 3-1 illustrates the client/server relational architecture of Pervasive.SQL. The client talks to the SQL Connection Manager on the server through TCP/IP or SPX. This architecture applies to the server engine and to the Workgroup engine (in the case where a client DSN is used to connect from the local Workgroup engine to the remote Workgroup engine).

Figure 3-2 illustrates the Workgroup relational architecture when an Engine DSN is used to connect from the local Workgroup engine to the remote database, assuming that a remote Workgroup engine is acting as a Gateway to the remote data.

 
Figure 3-1 Client/Server Relational Architecture

 
Figure 3-2 Workgroup Relational Architecture