One or more rows to be inserted in the batch insert procedure for table %1!s! were present in MSmerge_contents; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication.
One or more publications include tables with identity columns. At least one table has a larger identity range assigned to ...
One or more remote partitions have been selected. Queries that require redirection to the underlying data source will be ...
One or more rows deleted in table '%1!s!' were out of partition while the table was published with 'partition_options' set ...
One or more rows inserted in table '%1!s!' were out of partition while the table was published with 'partition_options' set ...
One or more rows to be inserted in the batch insert procedure for table %1!s! were present in MSmerge_contents; merge replication ...
One or more rows to be inserted in the batch insert procedure for table %1!s! were present in MSmerge_tombstone; merge replication ...
One or more rows to be updated for table %1!s! contain changes in the column %2!s!, which is used in one or more filters; ...
One or more rows updated in table '%1!s!' were out of partition while the table was published with 'partition_options' set ...
One or more schedules were not deleted because they are being used by at least one other job. Use "sp_detach_schedule" to ...