Partilhar via

How to: Recover or Move Notification Services Databases

  • Artigo

Many instances of Notification Services have databases on a remote database server. If your database server needs to be restored, or just the databases for the instance of Notification Services need to be restored, use the following procedure as a guideline for developing and testing your own recovery procedure.

Important

All deployments of Notification Services are unique. If you have a single-server deployment of Notification Services, use the following procedure as a guideline for developing and testing your own recovery procedure.

Step 1: Restore the databases and repair the instance of Notification Services

  1. Stop the instance of Notification Services on all servers that run the instance's engine components.

  2. If necessary, install the SQL Server 2005 Database Engine. For more information, see Installing SQL Server 2005.

  3. Restore any Microsoft Windows accounts and Microsoft SQL Server login accounts required by the instance of Notification Services.

  4. Restore and recover the instance and application databases.

    The exact procedures you use to restore a database depends on the recovery model. For more information about restoring databases, see Backing Up and Restoring How-to Topics (SQL Server Management Studio).

    If you are simply moving the databases to a new server, the Copy Database Wizard provides an easy way to copy databases. For more information, see Using the Copy Database Wizard.

  5. Run the nscontrol repair command to repair the Notification Services instance metadata:

    1. From the Start menu, point to All Programs\Microsoft SQL Server 2005\Configuration Tools, and then click Notification Services Command Prompt to open a command prompt window.

    2. nscontrol repair Command

      Note

      The repair command can be run from any computer that has the Notification Services engine or client components. If the instance of Notification Services is not registered, or the registry is out of date, provide the database server name in the nscontrol repair command.

Step 2: If the Database Engine instance name has changed, reregister and update the instance

  1. Update the registry on all servers that run a hosted event provider, distributor, generator, subscription management interface, non-hosted event provider, or other client application for the instance of Notification Services.

  2. Disable the instance of Notification Services.

  3. Modify the SQL Server system value in the instance configuration so that it references the correct instance of the Database Engine.

  4. Update the instance of Notification Services to apply the change to the instance database.

Step 3: Enable and start the instance of Notification Services

  1. Enable the instance of Notification Services.

  2. Start the instance of Notification Services on all servers that run the instance's engine components. If hosting the engine in a custom application, use the custom application to start the instance.

  3. Verify the status of the instance of Notification Services.

    Note

    It may take 30 seconds for the status to be updated.

See Also

Tasks

How to: Recover or Move a Single-Server Deployment of Notification Services
How to: Recover or Move Notification Services Client Components
How to: Recover or Move Notification Services Engine Components

Concepts

Recovering Instances of Notification Services

Other Resources

Administering Notification Services
Managing Instances and Applications How-to Topics (Notification Services)

Help and Information

Getting SQL Server 2005 Assistance