Este tema aún no ha recibido ninguna valoración - Valorar este tema

BusinessLogicModule.UpdateDeleteConflictHandler Method

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

Espacio de nombres: Microsoft.SqlServer.Replication.BusinessLogicSupport
Ensamblado: 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
)
public ActionOnUpdateDeleteConflict UpdateDeleteConflictHandler (
	SourceIdentifier updateSource, 
	DataSet sourceDataSet, 
	/** @ref */ DataSet customDataSet, 
	/** @ref */ ConflictLogType conflictLogType, 
	/** @ref */ String customConflictMessage, 
	/** @ref */ int historyLogLevel, 
	/** @ref */ String historyLogMessage
)
JScript no permite pasar argumentos de valor para referencia.

Parámetros

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.

Valor devuelto

The ActionOnUpdateDeleteConflict action that will be taken by the process after the custom business logic handler has executed.
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.

Plataformas de desarrollo

Para obtener una lista de las plataformas compatibles, vea Requisitos de hardware y software para instalar SQL Server 2005.

Plataformas de destino

Para obtener una lista de las plataformas compatibles, vea Requisitos de hardware y software para instalar SQL Server 2005.
¿Te ha resultado útil?
(Caracteres restantes: 1500)

Adiciones de comunidad

AGREGAR
© 2013 Microsoft. Reservados todos los derechos.