The copy or append table command follows a sequence of events when synchronizing a table. This solution delves on the feasibility of running the command concurrently for more than one table.
General information.
It is possible to run copy table or append table concurrently for more than one table. When doing so, it is important to understand the implications of what goes behind the scene at the Post side when running these commands. The Shareplex Reference Guide describes this under the section covering the copy/append:
"Running concurrent copy processes
You can issue multiple copy/append commands at a time. Users should note that while the copy process is in progress, the Post process stops all replication."
What it means is that the Post remains in suspended state till the copy/append finishes. So, essentially the Post will remain in suspended state till the copy/append finish for all the tables and not just one of them. Depending on the propensity of the users to tolerate the latency resulting from copy/append, it is possible to issue multiple sync commands. The latency will always be a function of the largest of the table being sync'd when concurrent copy/append are run and not the sum of the time taken for individual table.
