Sdílet prostřednictvím

Enabling and Disabling Instances, Applications, or Components

  • Článek

For maintenance or for troubleshooting reasons you might need to disable a deployed instance of Notification Services, disable a single application hosted by the instance, or disable a component of an instance or application.

Note

If you disable the generator component (or if you disable an instance or application), the clock that controls quantum processing stops. When you enable the generator, the generator attempts to catch up to the current real-time clock. This might have some impact on how quickly new notifications are generated, depending on the level of activity in the application. For information about controlling the quantum clock, see Specifying Quantum Limits.

Disabling Instances, Applications, or Components

The Disabled status allows you to pause an instance of Notification Services, a single application, or a single component.

When you disable an instance, application, or component, Notification Services records the state change in the instance or application database. Every 30 seconds, the Notification Services engine checks the database for the current status of its components. Between the time when you send the disable command and when the engine picks up the new status, the instance, application, or component reports its status as Disable Pending.

When you disable subscriber management, Notification Services simply sets a value in the database. The Notification Services engine does not run any subscriber management components, so there is no Disable Pending status.

To disable an instance of Notification Services
To disable an application or its individual components
To disable subscriber management

Enabling Instances, Applications, or Components

The Enabled status allows components to run. When you first create an instance of Notification Services, the instance is in the disabled state and must be enabled.

When you enable an instance, application, or component, Notification Services records the state change in the instance or application database. Every 30 seconds, the Notification Services engine checks the database for the current status of its components. Between the time when you send the enable command and when the engine picks up the new status, the instance, application, or component reports its status as Enable Pending.

When you enable subscriber management, Notification Services simply sets a value in the database. The Notification Services engine does not run any subscriber management components, so there is no Enable Pending status.

To enable an instance of Notification Services
To enable an application or its individual components
To enable subscriber management

See Also

Concepts

Starting and Stopping Instances of Notification Services
Viewing the Status of Instances, Applications, and Components

Other Resources

Administering Notification Services

Help and Information

Getting SQL Server 2005 Assistance