Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, errors will likely occur when moving data from the Publisher to the Subscriber.
Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with ...
Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %1!s! is missing under element. Consider ...
Cursor plan forcing failed because input plan has more than one node with OperationType=%1!s!. Consider using an XML cursor ...
Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch. ...
Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, ...
Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements. ...
Custom rollup formulas, custom member formulas, All member formulas, and custom level formulas are no longer supported as ...
Cyclical forwarding detected for event %1: Event source was '%2' which matches the current forwarding server. The event was ...
Czech, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...