Moving Instances of Notification Services
Typically when you move from the development phase to the test phase, or from the test phase to the production phase, you re-create the instance of Notification Services, which re-creates the databases used by the instance of Notification Services. However, if you want to keep the existing data, you can move the instance of Notification Services and its databases instead.
When you move an instance of Notification Services, besides the obvious step of installing software and moving files to the new server or servers, you must also update the instance of Notification Services to specify the name of the new instance of the Database Engine and the new system name for each hosted event provider, generator, and distributor. You must also make sure that the instance registration for engine components and client components point to the new instance of the Database Engine.
To move instances of Notification Services
- How to: Recover or Move a Single-Server Deployment of Notification Services
- How to: Recover or Move Notification Services Databases
- How to: Recover or Move Notification Services Engine Components
- How to: Recover or Move Notification Services Client Components
See Also
Other Resources
Backing Up and Recovering Notification Services
Updating Instances and Applications
Administering Notification Services