Re: OLEDB Provider with SQL Server 2000

Mark (swozz_@xxxxxxxxxxx) writes:
I have read this thread, Max's problem seems to be that SQL will ignore
indexes where it can't reliably estimate the cost of calling the
provider which seems to happen when he is doing joins, as far as I can
tell, SQL should still access the index for simple where clauses on
single tables, for instance...

SELECT * FROM <x> WHERE <col>=<val>

The problem I have is that I can't get SQL to take any interest in my
indexes at all! It doesn't even ask for the INDEXES schema!

I have done some tracing and discovered that SQL asks for a schema that
seems to be undocumented, it has a guid of
C8B52301-5CF3-11CE-ADE5-00AA0044773D and I can't find this anywhere!

I am using the ATL templates (although I wish I hadn't!) and I am starting
to think maybe there is something in the ATL source that stops support for
any schema other than TABLES/COLUMNS and PROVIDER TYPES, or maybe it is
because I am not supporting this mysterious schema!

I will have to admit that I have not tried to write my own provider,
even less trying to expose indexes in it. So the best I could was to
point you to that thread, as I recall Max gave some info on how make
the indexes visible.

But it is quite clear, that this is not a very well-documented area,
and only those for brave minds and time enough to trace what is going on.


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.

Relevant Pages

  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ERROR: Provider Management - Could not establish a connection to t
    ... If you have not yet created the SQL Server database, ... Can any data provider be used to ... Exception Details: System.Data.SqlClient.SqlException: A connection ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: .NET data provider or OLEDB provider?
    ... >I don't see where you see a built-in query engine. ... >service provider, ... >OLE DB providers don't have to support SQL however, ... > SQL Server linked server, SQL Server can handle the queries. ...
    (microsoft.public.data.oledb)
  • Re: Need Help: Operating system error 3706
    ... Installing an additional component resolved the problem and the software is now able to connect to the database ... The developer is currently doing a complete rewrite/update of the program, including database functions. ... While this would require a modest re-write, it's not that tough to convert to a managed-code provider instead of the COM-based OLE DB provider. ... If the application is not based on .NET, then make sure the application is upgraded to use the SNAC (SQL Server Native Client) provider which is less trouble-prone than the older MDAC-based providers. ...
    (microsoft.public.sqlserver.connect)
  • Re: ERROR: Provider Management - Could not establish a connection to t
    ... If you have not yet created the SQL Server database, ... Can any data provider be used to ... pipes and I have the server configured to connect using TCP/IP. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading