> Is it possible to add index only for "EnvelopeID" since only this field is in
> where clause?
If you know that it will always be the EnvelopeID field that you want
to look up in the index, you can limit the index entries to this field
(e.g. by setting TEXTINCLUDE to "*:EnvelopeID" as an option
Christian,
Is it possible to add index only for "EnvelopeID" since only this field is in
where clause?
May be it will speed up the queries..
24.05.2018, 14:47, "Ветошкин Владимир" :
> Thank you Christian for your kind words :)
>
> I rewrote queries as you said.
> It helped
> I thought about "random access patterns"
> But all databases are on one disk.
I agree, this sounds confusing at first sight. Some more details: If
the same database is opened by multiple queries, only one instance
will be opened. The same data cursor is used to read data, and if the
data is
Hi, Christian!
Thank you for your reply!
I attached the file.
I thought about "random access patterns"
But all databases are on one disk.
So, why two queries to different databases complete in about 5 sec?
And if these queries make to one database - it takes a long time...
> by setting the
Hi Ветошкин (cc to the list),
Maybe we find a way to speed up your queries; you can attach them to
your next mail.
I guess that the parallel query execution leads to "random access
patterns" on disk. You can enforce one query at a time by setting the
PARALLEL option to 1 (see [1]).
Hope this
Привет Ветошкин,
Welcome to the list. Just send your question to this address.
Best,
Christian
Ветошкин Владимир schrieb am Mi., 23. Mai 2018, 19:10:
> Hello!
>
> Sorry for my English.
> May I ask you some questions here or I have to write them on github?
>
> --
>
Hello!
Sorry for my English.
May I ask you some questions here or I have to write them on github?
--
С уважением,
Ветошкин Владимир Владимирович
7 matches
Mail list logo