Microsoft.SqlServer.Replication.BusinessLogicSupport

This assembly provides business logic that can be used in your application to respond to a number of conditions that occur during synchronization: data changes, conflicts, and errors. To create your own business logic handler, you must implement the specific methods of the class that are required by your application. For more information on business logic handlers, see Executing Business Logic During Merge Synchronization.

Enumerates all actions that can be taken when handling data changes that do not result in a conflict.

The data change is overridden by custom user data provided by the business logic handler. The custom user data is then propagated by the replication process.

The data change is accepted and propagated by the replication process as usual.

The data change is rejected and not propagated by the replication process.

Enumerates all actions that can be taken when replicating DELETE statements that do not result in a conflict.

The delete is accepted and propagated by the replication process as usual.

The delete is rejected, and the change row should be updated on the destination so that it becomes an insert on the source of the original delete.

The delete is rejected and not propagated by the replication process.

Enumerates all actions that can be taken when handling data errors.

The error is handled using custom user functionality provided by the business logic handler. The custom functionality is then propagated by the replication process.

The error is handled by replication using default error behaviors.

Enumerates all actions that can be taken when handling conflicting UPDATE statements.

The conflict is resolved using custom user data provided by the business logic handler. The custom data is then propagated by the replication process.

The conflict is resolved using the default resolution rules.

The conflict is resolved by accepting the update from the Publisher as the winning update.

The conflict is resolved by accepting the update from the Subscriber as the winning update.

Enumerates all actions that can be taken when handling an UPDATE statement that conflicts with a DELETE statement.

The conflict is resolved using custom user data provided by the business logic handler. The custom user data is then propagated by the replication process.

The conflict is resolved using the default resolution rules

The conflict is resolved by accepting the delete as the winner.

The conflict is resolved by accepting the update as the winner.

Implements the custom business logic that is invoked during the merge replication synchronization process.

Constructor.

Optional method implements the custom business logic that is invoked when a data change is committed during synchronization.

that indicates whether the source of the change is the Publisher or the Subscriber. GUID of the row that was committed.

Optional method that implements the custom business logic invoked when an error occurs at the time a DELETE statement is being uploaded or downloaded.

The action that will be taken by the process after the custom business logic handler has executed. that indicates whether the source of the delete that generated the error is the Publisher or the Subscriber. Dataset that contains the GUID of the row that was deleted. output parameter that controls how replication logs the error. This parameter is used only if the return value is . Output parameter used to return a custom error message. This parameter is used only if the return value is . Error code that corresponds to the underlying replication error that occurred. Error message text that corresponds to the underlying replication error that occurred. Log level of the custom message returned by the custom business logic handler. Log message provided by the custom business logic handler. The log message gets written to the distribution database.

Optional method that implements the custom business logic invoked when DELETE statements are being uploaded or downloaded.

The action that will be taken by the process after the custom business logic has executed. Specifies whether the delete is initiated at the Publisher or at the Subscriber. Dataset containing the GUID of the row that was deleted. Log level of the custom message returned by the custom business logic. Log message provided by the custom business logic. The log message gets written to the distribution database.

Disposes of all used resources. This method is invoked after all the custom business logic has been executed.

Sends information about the article being synchronized to the business logic resolver when the Merge Agent is started.

Name of the Publisher. Name of the Subscriber. Name of the Distributor. Name of the publication database. Name of the subscription database. Name of the published article.

Optional method implements the custom business logic invoked when an error occurs at the time an INSERT statement is being uploaded or downloaded.

The action that will be taken by the process after the custom business logic handler has executed. that indicates whether the source of the insert that generated the error is the Publisher or the Subscriber. Dataset that contains the GUID of the row that was inserted. output parameter that controls how replication logs the error. This parameter is used only if the return value is . Output parameter used to return a custom error message. This parameter is only used if the return value is . Error code that corresponds to the underlying replication error that occurred. Error message text that corresponds to the underlying replication error that occurred. Log level of the custom message returned by the custom business logic handler. Log message provided by the custom business logic handler. The log message gets written to the distribution database.

Optional method that implements the custom business logic invoked when INSERT statements are being uploaded or downloaded.

The action that will be taken by the process after the custom business logic has executed. that defines whether the insert was initiated at the Publisher or the Subscriber. Dataset that contains the GUID of the row that was inserted. Dataset that contains the modified row returned by the custom business logic. Log level of the custom message returned by the custom business logic. Log message provided by the custom business logic. The log message gets written to the distribution database.

Optional method that indicates the beginning of an upload or download phase of the synchronization.

Specifies whether the phase about to begin is an upload or download.

Optional method that implements the custom business logic invoked when conflicting UPDATE statements occur at the Publisher and at the Subscriber.

The action that will be taken by the process after the custom business logic handler has executed. Dataset representing the Publisher data. Dataset representing the Subscriber data. Dataset implemented by the custom business logic. requested by the custom business logic handler. Conflict message returned by the custom business logic handler. Log level of the custom message returned by the custom business logic handler. Log message provided by custom business logic handler. The log message gets written to the distribution database.

Optional method that implements the custom business logic invoked when UPDATE statements conflict with DELETE statements at the Publisher and at the Subscriber.

The action that will be taken by the process after the custom business logic handler has executed. Is the that indicates whether the source of the update is the Publisher or the Subscriber. Dataset that contains the GUID representing the row in conflict. Dataset implemented by the custom business logic. requested by the custom business logic handler. Conflict message returned by the custom business logic handler. Log level of the custom message returned by the custom business logic handler. Log message provided by custom business logic handler. The log message gets written to the distribution database.

Optional method that implements the custom business logic invoked when an error occurs at the time an UPDATE statement is being uploaded or downloaded.

The action that will be taken by the process after the custom business logic handler has executed. that indicates whether the source of the update that generated the error is the Publisher or the Subscriber. Dataset representing the UPDATE statement that caused the error. output parameter that controls how replication logs the error. This parameter is used only if the return value is . Output parameter used to return a custom error message. This parameter is used only if the return value is . Error code that corresponds to the underlying replication error that occurred. Error message text that corresponds to the underlying replication error that occurred. Log level of the custom message returned by the custom business logic handler. Log message provided by custom business logic handler. The log message gets written to the distribution database.

Optional method that implements the custom business logic invoked when UPDATE statements are being uploaded or downloaded.

The action that will be taken by the process after the custom business logic has executed. Specifies whether the update was initiated at the Publisher or at the Subscriber. Dataset representing the data being updated. Dataset implemented by the custom business logic. Log level of the custom message returned by the custom business logic. Log message provided by custom business logic. The log message gets written to the distribution database.

Required property that returns information on the types of changes handled by the business logic module.

that enumerates the types of changes handled by the business logic module.

Enumerates all data change states that custom business logic can handle during synchronization.

When changes are committed to the destination database.

When an error occurs while propagating a DELETE statement from the Publisher to the Subscriber.

When a DELETE statement at the Publisher is applied at the Subscriber.

When an error occurs while propagating an INSERT statement from the Publisher to the Subscriber.

When an INSERT statement at the Publisher is applied at the Subscriber.

When an error occurs while propagating an UPDATE statement from the Publisher to the Subscriber.

When an UPDATE statement at the Publisher is applied at the Subscriber.

When an UPDATE statement at the Publisher conflicts with a DELETE statement at the Subscriber.

When an error occurs while propagating a DELETE statement from the Subscriber to the Publisher.

When a DELETE statement at the Subscriber is applied at the Publisher.

When an error occurs while propagating an INSERT statement from the Subscriber to the Publisher.

When an INSERT statement at the Subscriber is applied at the Publisher.

When an error occurs while propagating an UPDATE statement from the Subscriber to the Publisher.

When an UPDATE statement at the Subscriber conflicts with a DELETE statement at the Publisher.

When an UPDATE statement at the Subscriber is applied at the Publisher.

When an UPDATE statement at the Publisher conflicts with an UPDATE statement at the Subscriber.

Enumerates the supported conflict logging options available to a conflict handler.

The conflict is not logged.

The Publisher's dataset is logged as the conflict loser.

The Subscriber's dataset is logged as the conflict loser.

Enumerates the supported error logging options available.

The custom error information is logged.

The error is not logged.

Enumerates all sources of a data change.

Data change occurred at the Publisher.

Data change occurred at the Subscriber.