Re: OLEDB Provider with SQL Server 2000
- From: "Mark" <swozz_@xxxxxxxxxxx>
- Date: Wed, 1 Mar 2006 14:04:44 -0000
It seems SQL asks for 2 additional schemas
C8B52301-5CF3-11CE-ADE5-00AA0044773D DBSCHEMA_CHECK_CONSTRAINTS_BY_TABLE
C8B522FF-5CF3-11CE-ADE5-00AA0044773D DBSCHEMA_TABLE_STATISTICS
I will build some support for these and see if it kicks SQL into requesting
my INDEX/TABLE_INFO schemas.
--
Best regards
Mark
"Mark" <swozz_@xxxxxxxxxxx> wrote in message
news:exWlchTPGHA.720@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Erland,
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!
--
Best regards
Mark
"Erland Sommarskog" <esquel@xxxxxxxxxxxxx> wrote in message
news:Xns97783C2BF843Yazorman@xxxxxxxxxxxx
Mark (swozz_@xxxxxxxxxxx) writes:
I have written an OLEDB Provider to access our propriety format database
through SQL Server 2000 as a remote server. This works fine, now I am
trying to implement index support. I have set the "Index as access path"
provider option and implemented the index schema rowset but SQL 2000
doesn't seem interested in using my indexes, it doesn't even request the
index schema!
Does anybody have any information on how SQL 2000 determines if it
should
use a particular index?
We had a looong thread about this in October. The outcome was not
entirely
conclusive, but may you find it worthwhile to review it on
http://groups.google.com/group/microsoft.public.data.oledb/browse_frm/thread/6ceeafc2faa35d9/257021f6aebd9e23?tvc=1&q=group%3Amicrosoft.public.data.oledb+author%3AErland+author%3ASommarskog&hl=sv#257021f6aebd9e23
--
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
.
- References:
- Re: OLEDB Provider with SQL Server 2000
- From: Mark
- Re: OLEDB Provider with SQL Server 2000
- Prev by Date: Re: OLEDB Provider with SQL Server 2000
- Next by Date: UPDATE statement on an MDB
- Previous by thread: Re: OLEDB Provider with SQL Server 2000
- Next by thread: Re: OLEDB Provider with SQL Server 2000
- Index(es):
Relevant Pages
|