Remote Connections

In past versions of the provider, you had to specify a full path to the DDFs in order to have remote access.

Now, the provider connects to the engine via a network protocol. The server engine processes the request, then sends the data back for the provider for processing and hand-off to the client. This is accomplished using the same protocol as the ODBC client.

Transactional access has not changed. The transactional engine is still on the client side, because remoting the transactional engine would have degraded performance.

New Syntax Supported

You can specify the remote server using the Location= parameter in the connection string.

Provider=PervasiveOLEDB;Data 
Source=MyDBname;Location=MyServer 
 


 Note


The data source parameter refers to a database name (DBname), not a DSN. DSNs are only used in ODBC.

Backward Compatibility

If you are currently using a path to the DDFs from your connection string, this method is still supported.

Provider=PervasiveOLEDB;Data Source=f:\mydata

Unlike previous versions of Pervasive.SQL, it is required that a DBname exist on the server to which you are connecting.

There is no performance difference between specifying a database name and a Location, or specifying a mapped drive. However, using a Location is the recommended way of connecting to a remote server. The OLE DB provider may have permissions issues when using a mapped drive or UNC path.

Note
If you are using the OLE DB provider in conjunction with a mapped drive or UNC path in the Data Source portion of the connection string, please also see Using the OLE DB Provider with a UNC Path or Mapped Drive .