[AccessD] ADO Recordset Procedure markedly slower with 'newer' data?

[Bill Benson]

Isn’t there some kind of queryplanner thingamabob that kicks in and
translates even fairly inefficient queries into more efficient versions so
that the database doesn’t really run “your” query, but one it has optimized
on your behalf? Or am I in fantasy land?

On Thu, Apr 29, 2021 at 1:09 PM Ryan W <wrwehler at gmail.com> wrote:

> Sorry for the late reply. I do not have a cover index for this data, but I
> did re-write part of the query to use a subquery and it sped it up a whole
> bunch on that data. So maybe it was just inefficient to start with.
>
> On Wed, Apr 28, 2021 at 5:23 PM John Colby <jwcolby at gmail.com> wrote:
>
> > Possibly a "cover index" in SQL Server not covering a field used in that
> > year data?  It feels like an index problem.
> >
> >
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>