Partilhar via

BusinessLogicModule.UpdateDeleteConflictHandler Method

  • Artigo

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)

Syntax

'Declaration
Public Overridable Function UpdateDeleteConflictHandler ( _
    updateSource As SourceIdentifier, _
    sourceDataSet As DataSet, _
    ByRef customDataSet As DataSet, _
    ByRef conflictLogType As ConflictLogType, _
    ByRef customConflictMessage As String, _
    ByRef historyLogLevel As Integer, _
    ByRef historyLogMessage As String _
) As ActionOnUpdateDeleteConflict

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

public:
virtual ActionOnUpdateDeleteConflict UpdateDeleteConflictHandler (
    SourceIdentifier updateSource, 
    DataSet^ sourceDataSet, 
    DataSet^% customDataSet, 
    ConflictLogType% conflictLogType, 
    String^% customConflictMessage, 
    int% historyLogLevel, 
    String^% historyLogMessage
)

public ActionOnUpdateDeleteConflict UpdateDeleteConflictHandler (
    SourceIdentifier updateSource, 
    DataSet sourceDataSet, 
    /** @ref */ DataSet customDataSet, 
    /** @ref */ ConflictLogType conflictLogType, 
    /** @ref */ String customConflictMessage, 
    /** @ref */ int historyLogLevel, 
    /** @ref */ String historyLogMessage
)

JScript does not support passing value-type arguments by reference.

Parameters

  • updateSource
    Is the SourceIdentifier that indicates whether the source of the update is the Publisher or the Subscriber.
  • sourceDataSet
    Dataset that contains the GUID representing the row in conflict.
  • customDataSet
    Dataset implemented by the custom business logic.
  • conflictLogType
    ConflictLogType requested by the custom business logic handler.
  • customConflictMessage
    Conflict message returned by the custom business logic handler.
  • historyLogLevel
    Log level of the custom message returned by the custom business logic handler.
  • historyLogMessage
    Log message provided by custom business logic handler. The log message gets written to the distribution database.

Return Value

The ActionOnUpdateDeleteConflict action that will be taken by the process after the custom business logic handler has executed.

Thread Safety

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Platforms

Development Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

Target Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

See Also

Reference

BusinessLogicModule Class
BusinessLogicModule Members
Microsoft.SqlServer.Replication.BusinessLogicSupport Namespace

Other Resources

Executing Business Logic During Merge Synchronization
How to: Implement a Business Logic Handler for a Merge Article (Replication Programming)