Microsoft Knowledge Base Email Alertz

(242260) - The OLE DB Simple Provider (OSP) Toolkit is geared toward making simple OLE DB data providers. It basically exposes core OLE DB interfaces and capabilities. The default implementation of such a simple OLE DB data provider will not work with the Data...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 242260 - Last Review: October 17, 2003 - Revision: 2.1

INFO: Cannot Use OSP Data Providers with SQL DTS

This article was previously published under Q242260

SUMMARY

The OLE DB Simple Provider (OSP) Toolkit is geared toward making simple OLE DB data providers. It basically exposes core OLE DB interfaces and capabilities. The default implementation of such a simple OLE DB data provider will not work with the Data Transformation Services (DTS) provided by SQL Server 7.0.

This article describes the limitation of using the OSP data providers with DTS in SQL Server 7.0.

MORE INFORMATION

In order to use any OLE DB provider with DTS through the DTS Designer and DTS Wizard, the following OLE DB interfaces must be implemented in the Data Provider:
   IDBInitialize 
   IDBProperties 
   IDBCreateSession 
   ISessionProperties 
   IDBInfo 
   IColumnsInfo 
   IRowset 
   IAccessor 
   IOpenRowset 
   IDBSchemaRowset 
   ITransactionJoin: If using transactions across steps
				
However, the OSP Toolkit does not expose the following Extended OLE DB interfaces that must be supported when using DTS:
   IDBInfo
   IDBSchemaRowset
   ITransactionJoin
				


In order to use your OLE DB provider within the Data Transformation Services, you should consider building an OLE DB provider using Microsoft Visual C++ rather than with the OSP interfaces. Although writing providers with Microsoft Visual C++ involves a greater development effort, the providers you write will provide you with greater extensibility and a richer set of OLE DB data manipulation routines.

REFERENCES

For additional information, please click the article number(s) below to view the article(s) in the Microsoft Knowledge Base:
241241  (http://kbalertz.com/Feedback.aspx?kbNumber=241241/EN-US/ ) INF: Using DTS With Custom ATL OLE-DB Providers
185822  (http://kbalertz.com/Feedback.aspx?kbNumber=185822/EN-US/ ) INFO: Creating Robust OLE DB Providers with OSP
For additional documentation, use the following references:

"Supported OLE DB Interfaces" in the OSP Toolkit documentation in Data Access SDK.The Visual Basic Documentation (c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Ammar Abuthuraya, Microsoft Corporation.


APPLIES TO
  • OLE DB Simple Provider Toolkit 2.0
  • OLE DB Simple Provider Toolkit 1.5
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbdatabase kbinfo kbprovider KB242260
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate