Overview of the OLE DB Remoting Provider

The OLE DB Remoting Provider is an OLE DB service provider with its own properties and settings, making it possible to code directly to this provider from your applications. You call the Remoting Provider the same way you code to other OLE DB providers, such as the OLE DB Provider for Microsoft Indexing Service and the OLE DB Provider for SQL Server.


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.

Who can use this provider

ADO and OLE DB developers who want to access OLE DB data providers that run on separate machines or in separate processes on the same machine can use this provider.

What this provider allows you to do

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 Microsoft Cursor Service for OLE DB and the Persistence Provider, the Remoting Provider allows you to retrieve rowsets from remote data stores and update those rowsets.

Remote data providers are defined as those running on the same computer as the consumer but in a different process, or they can be providers that are running on another computer. When running on another computer, the Remoting Provider communicates over the network using either DCOM or HTTP protocol.

The client application benefits from the full power of OLE DB, but all the remoting services are handled outside the application. This increases scalability. The client application need not change when the location of the data store changes.


For more information, including recent technical articles, see the Microsoft Data Access and Storage Developer Center in the MSDN Library.