Database Supplemental logging with Primary Key is turned on.
Shareplex Horizontal Replication is in use.
But reader performance is slow.
Reader should be processing a lot of updates.
Horizontal partitioning is configured on a column (say column1) which is not part of primary key.
Supplemental logging on column1 is not on.
To process the updates reader queries the database on the column1 condition to determine the queue in which the message has to go.
This slows down the reader performance.
Resolution 1:
Include column1 as part of the primary key and enable supplemental logging on Primary Key for this table
Resolution 2:
Turn on the supplemental logging for column1.
Resolution 3:
Configure this table with out horizontal partitioning.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center