Invoking the OLE DB Remoting Provider
Important
This feature will be removed in a future version of Windows. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Applications should instead use WCF Data Service.
The OLE DB Remoting Provider enables those applications written to consume data from OLE DB providers to work with remote OLE DB data providers. Used in conjunction with other service components, such as the Cursor Service and the Persistence Provider, the Remoting Provider allows you to retrieve rowsets from remote data stores and update those rowsets.
Note
The following sample code uses SQL Server authentication. If you connect to a data source provider that supports Windows authentication, use trusted_connection or Integrated Security syntax.
Invoking the Remoting Provider is similar to invoking other OLE DB providers. The basic connection string is similar, as shown in this example:
Data Source=Pubs;User ID=eem;Password=pwd
To identify the remote location, server, and the data provider residing on the remote server, the following code is prefaced to the connection string:
Provider=MS Remote;Remote Server=http://webaddress;
Remote Provider=SQLOLEDB;Data Source=Pubs;User ID=eem;Password=pwd
Connection string keyword |
Description |
|---|---|
Provider |
Value is "MS Remote". |
Remote Server |
Location of the remote server written as the full address. |
Remote Provider |
Identifies the data provider on the remote computer. |
Data Source |
Identifies the name of the remote data store. |
User ID |
Identifies the user. |
Password |
Identifies the password. |
When called, the local copy of the Remoting Provider connects using the address given with the Remote Server keywords. The DataFactory object on the remote server then calls the identified Remoting Provider and passes the connection information to it.