OpenEdge Data Management: DataServer for Microsoft SQL Server

Introduction
1–12
With the MS SQL Server client software-supplied modules that manage networked database
communications, a remote database configuration is possible. The DataServer cares only about
the local MS SQL Server data source definition. Remote database access is transparent to the
DataServer.
The remote DataServer configuration
Figure 1–5 shows the remote DataServer configuration.
Schema
holder
Figure 1–5: The remote DataServer for MS SQL Server
In the remote configuration, the OpenEdge client and schema holder run on a client machine
and the OpenEdge server components and any MS SQL Server client software run on a remote
server machine. The actual target database can be local or remote to the machine where the
OpenEdge DataServer for MS SQL Server executes. With the MS SQL Server client software
supplied modules that manage networked database communications, a remote database
configuration is possible. The DataServer cares only about the data source definition on its
machine. Remote database access is transparent to the DataServer.
In remote DataServer configurations, OpenEdge handles the communication between the client
and the server. The client and server processes that make up the DataServer adapt to a variety
of network configurations.
Table 1–2 lists the supported configurations for setting up a remote DataServer. It contains
possible client-server combinations and networking options.
Table 1–2: Supported configurations
Client Networking Server
OpenEdge client in
Windows
OpenEdge client in
Windows or on UNIX
OpenEdge
client
OpenEdge
networking
DataServer
ODBC driver
data-source
client software
Server components
Data
source
None The server, client, ODBC client, and data
source are on the same machine.
OpenEdge The client can reside in Windows or on
UNIX. The server, ODBC driver, and
data source are on a Windows server
machine.