Thanks James,
It is a good idea. The situation is that my customer will give different
numbers of "in" conditions randomly. So sometimes there is 10 point lookups for
a sql while sometimes there could be 100 thousand point lookups. If I change
the guidepost width to a smaller digit
, the
The finest granularity we have available is to specify a guidepost width at
the table level with the GUIDEPOSTS_WIDTH=## property. This will take
effect for that table next time stats are collected (on a major compaction
or when collected manually through the UPDATE STATISTICS command).
On Tue,
Hi there,
I am optimizing an sql that is compiled to point lookups. Since sometimes there
could be many thousands of "in" conditions in the sql, I would like to increase
the parallelism number for better performance. I know that I can increase the
salted bucket number or decrease the guide
