How to: Recover or Move Notification Services Databases

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

   • How to: Stop an Instance of Notification Services (SQL Server Management Studio)
     
   • How to: Stop an Instance of Notification Services (Services Manager)
     
   • How to: Stop an Instance of Notification Services (Command Prompt)
     

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.

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.

   • How to: Register an Instance of Notification Services for Engine Components (SQL Server Management Studio)
     
   • How to: Register an Instance of Notification Services for Client Components (SQL Server Management Studio)
     
   • nscontrol register Command
     

     Note:
     If you host the Notification Services engine in a custom application, do not create the Windows service. For more information, see Hosting the Notification Services Engine.

2. Disable the instance of Notification Services.

   • How to: Disable an Instance of Notification Services (SQL Server Management Studio)
     
   • nscontrol disable Command
     

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.

   • How to: Update an Instance of Notification Services (SQL Server Management Studio)
     
   • nscontrol update Command
     

1. Enable the instance of Notification Services.

   • How to: Enable an Instance of Notification Services (SQL Server Management Studio)
     
   • nscontrol enable Command
     

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.

   • How to: Start an Instance of Notification Services (SQL Server Management Studio)
     
   • How to: Start an Instance of Notification Services (Services Manager)
     
   • How to: Start an Instance of Notification Services (Command Prompt)
     

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

   • How to: View the Status of a Notification Services Instance (SQL Server Management Studio)
     
   • nscontrol status Command
     

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

Tasks

Concepts

Other Resources

Help and Information