At times there are batch jobs run on source database that can cause backlogging of queues, slowness of Shareplex processes, delay in posting to the target database resulting in latency, etc. All this is due to the way the transaction is done on the source. The management may want to identify the user or application that ran the transaction on the source. The question arises as to whether this can be inferred with the help of shareplex.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center