This documentation is archived and is not being maintained.

Starting and Stopping Instances of Notification Services

When you define a Notification Services application, you specify the server that runs each hosted event provider, generator, and distributor. The Notification Services engine, which is typically the NS$instanceName Microsoft Windows service, runs these components. To start an instance of Notification Services on a server, you start the Notification Services engine, which typically means starting the Windows service.

When you start an instance of Notification Services, the engine gets the database server name from the registry and checks the instance database and application databases to determine which components run on its server. The engine also checks whether those components are enabled or disabled. All enabled components start processing data. All disabled components are paused and do not process data until enabled.

While the engine is running, it checks the enabled or disabled status of its components every 30 seconds. If the status of any component changes, that component goes through a startup or shutdown sequence.

If the NS$instanceName Windows service runs the Notification Services engine, you can start the Notification Services engine through the Services Manager, the Command Prompt window, or SQL Server Management Studio. If the engine is hosted in a custom application, you must use the application to start the instance of Notification Services.

Stopping the Notification Services engine stops the processing of the engine components on the server. If your instance of Notification Services is scaled out across multiple servers, the engine components on other servers continue to run until they are disabled, or the engine is stopped on those servers.

If the NS$instanceName Windows service runs the Notification Services engine, you can stop the instance of Notification Services through the Services Manager, the Command Prompt window, or SQL Server Management Studio. If the engine is hosted in a custom application, you must use the application to stop the instance of Notification Services.

Show: