Export (0) Print
Expand All

BusinessLogicModule.UpdateDeleteConflictHandler Method

Topic Status: Some information in this topic is pre-release and subject to change in future releases. Pre-release information describes new features or changes to existing features in Microsoft SQL Server 2014.

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

Namespace:  Microsoft.SqlServer.Replication.BusinessLogicSupport
Assembly:  Microsoft.SqlServer.Replication.BusinessLogicSupport (in Microsoft.SqlServer.Replication.BusinessLogicSupport.dll)

public virtual ActionOnUpdateDeleteConflict UpdateDeleteConflictHandler(
	SourceIdentifier updateSource,
	DataSet sourceDataSet,
	ref DataSet customDataSet,
	ref ConflictLogType conflictLogType,
	ref string customConflictMessage,
	ref int historyLogLevel,
	ref string historyLogMessage


Type: Microsoft.SqlServer.Replication.BusinessLogicSupport.SourceIdentifier
Is the SourceIdentifier that indicates whether the source of the update is the Publisher or the Subscriber.
Type: DataSet
Dataset that contains the GUID representing the row in conflict.
Type: DataSet
Dataset implemented by the custom business logic.
Type: Microsoft.SqlServer.Replication.BusinessLogicSupport.ConflictLogType
ConflictLogType requested by the custom business logic handler.
Type: String
Conflict message returned by the custom business logic handler.
Type: Int32
Log level of the custom message returned by the custom business logic handler.
Type: String
Log message provided by custom business logic handler. The log message gets written to the distribution database.

Return Value

Type: Microsoft.SqlServer.Replication.BusinessLogicSupport.ActionOnUpdateDeleteConflict
The ActionOnUpdateDeleteConflict action that will be taken by the process after the custom business logic handler has executed.

Community Additions

© 2014 Microsoft