Application.SubscriptionQuantumLimit Property

Gets or sets a value that specifies how far the logical (quantum) clock can fall behind the real-time clock before skipping subscription rule firings.

Espacio de nombres: Microsoft.SqlServer.Management.Nmo
Ensamblado: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)

Sintaxis

'Declaración
Public Property SubscriptionQuantumLimit As Integer

public int SubscriptionQuantumLimit { get; set; }

public:
property int SubscriptionQuantumLimit {
    int get ();
    void set (int value);
}

/** @property */
public int get_SubscriptionQuantumLimit ()

/** @property */
public void set_SubscriptionQuantumLimit (int value)

public function get SubscriptionQuantumLimit () : int

public function set SubscriptionQuantumLimit (value : int)

Valor de propiedad

A Int32 that specifies a number of quantum clock intervals.

Notas

Texto actualizado:5 de diciembre de 2005

Notification Services uses a quantum clock to schedule rule firings. If the Notification Services engine that runs the application was down, or if the workload is causing the application to fall behind, the quantum clock can fall behind the real-time clock. This means that Notification Services falls behind on maintaining the running subscription rules.

Quantum limits ensure that the application does not fall too far behind the real-time clock, helping to ensure that newer data is processed in a timely manner.

If you use the Application(Instance,String) constructor, the default value is 30 quanta, which is 30 minutes, assuming a default QuantumDuration value of 1 minute. If you use the default constructor, you must set this property.

0 indicates no subscription quantum limit. No subscription rule firings are skipped.

Ejemplo

The following examples show how to set all application execution settings, including the subscription quantum limit:

// Define application execution settings
myApplication.QuantumDuration = new TimeSpan(0, 0, 15);
myApplication.PerformanceQueryInterval = new TimeSpan(0, 0, 5);
myApplication.SubscriptionQuantumLimit = 1;
myApplication.ChronicleQuantumLimit = 1;
myApplication.VacuumRetentionAge = new TimeSpan(0, 0, 1);
myApplication.LogBeforeDeliveryAttempts = false;
myApplication.LogNotificationText = false;
myApplication.LogStatusInfo = false;
myApplication.EventThrottle = 500;
myApplication.NotificationThrottle = 500;
myApplication.SubscriptionThrottle = 500;
myApplication.ProcessEventsInOrder = false;

' Define application execution settings
myApplication.QuantumDuration = New TimeSpan(0, 0, 15)
myApplication.PerformanceQueryInterval = New TimeSpan(0, 0, 5)
myApplication.SubscriptionQuantumLimit = 1
myApplication.ChronicleQuantumLimit = 1
myApplication.VacuumRetentionAge = New TimeSpan(0, 0, 1)
myApplication.LogBeforeDeliveryAttempts = False
myApplication.LogNotificationText = False
myApplication.LogStatusInfo = False
myApplication.EventThrottle = 500
myApplication.NotificationThrottle = 500
myApplication.SubscriptionThrottle = 500
myApplication.ProcessEventsInOrder = False

Seguridad para subprocesos

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

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.

Vea también

Referencia

Application Class
Application Members
Microsoft.SqlServer.Management.Nmo Namespace

Otros recursos

Especificar límites de cuantos
SubscriptionQuantumLimit Element (ADF)