| SQL Server Setup Help | |
| How to: Migrate Notification Services Instances to a Higher Edition (Command Prompt) | |
See Also
|
|
|
| Upgrading SQL Server Components > Upgrading SQL Server Components How-to Topics > Migrating Notification Services How-to Topics > |
If you create an instance of Notification Services using a lower edition of Microsoft SQL Server 2005, such as Standard Edition, and later want to upgrade to a higher edition of SQL Server, such as Enterprise Edition, you must migrate the instance of Notification Services to match the database server. The following procedure shows how to migrate a Notification Services instance to a higher edition using command-prompt utilities.
 Important: |
|---|
| Instances of Notification Services can be deployed in many different configurations. Use the following procedure as a guideline for developing and testing your own migration procedures. |
To upgrade to a higher edition of Notification Services
-
On one server where the instance is registered, disable the instance:
-
On the Start menu, point to All Programs\Microsoft SQL Server 2005\Configuration Tools, and then click Notification Services Command Prompt.
-
Type the following command to disable the instance:
nscontrol disable -name instanceName
-
On the Start menu, point to All Programs\Microsoft SQL Server 2005\Configuration Tools, and then click Notification Services Command Prompt.
-
On each server where the instance is running, type the following command to stop the instance:
net stop NS$ instanceName
If you are hosting the engine components in your own application, make sure the instance is not running.
-
On each server where the instance of Notification Services is installed, upgrade Notification Services to the higher edition.
-
On one server, type the following command to upgrade metadata in the databases:
nscontrol upgrade -name instanceName -server databaseServer
Exact arguments vary depending on the security configuration.
-
On one server, type the following command to update metadata in the databases:
nscontrol update -in ICFPath\ICFName.xml
Exact arguments vary depending on the security configuration.
-
On each server that runs an NS$instanceName Windows service, type the following to start the service:
net start NS$ instanceName
If you are hosting the engine components in your own application, start the instance.
-
On one server, type the following command to enable the instance:
nscontrol enable -name instanceName