Progress
DataServer for
Microsoft SQL Server
Guide


The Remote DataServer Configuration

Figure 1–5 shows the remote DataServer configuration.

Figure 1–5: The Remote DataServer for SQL Server™

In the remote configuration, the Progress client and schema holder run on a client machine and the Progress server components and any SQL Server™ client software run on a remote server machine. The actual target database may be local or remote to the machine where the Progress DataServer for SQL Server™ executes. With the 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, Progress 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
Progress on Windows and NT
None
The server, client, ODBC client, and data source are on the same machine.
You can configure both the Personal and Enterprise DataServers for SQL Server™ in this way. (The Personal DataServer for SQL Server™ is restricted to single-user Windows platforms only.)
Progress on Windows, NT, and UNIX
Progress
The client can reside on Windows, NT, or Unix. The server, ODBC driver, and data source are on a NT server machine.
This configuration is possible only with the Enterprise DataServer for SQL Server™.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095