A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and could not be resolved automatically. The incoming delete was skipped by peer %3!s!. The conflict has to be resolved manually to guarantee data convergence between the peers. For steps on how to resolve the conflict refer to BOL.
A DEFAULT constraint cannot be created on the column '{0}' in the table '{1}' because the column is a sparse column or sparse ...
A default instance of SQL Server 2000 (64-bit) Analysis Services was detected. To continue, install a named instance of SQL ...
A definition for the '%{strAttrID/}' attribute is missing, although the attribute is specified as a new related attribute ...
A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. ...
A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and could not be resolved automatically. ...
A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and resolved. The incoming delete ...
A destination property was specified on a property mapping that is invalid. This occurs when a property is specified on a ...
A dimension exists that does not have exactly one attribute for original ID, effective start date, effective end date, and ...
A distributor failed to give a buffer to thread "%1!s!" because of error 2!8.8X!. The target thread is probably shutting ...