Connecting Business Notification to multiple NAV databases

Theo_van_de_Ven

For one of our customers I have succesfully installed a Business Notification server that connects to a Navision database.

This customer does have 3 Navision databases (SQL 2000). Database 1 will be used to develop in. Database 2 will be used as an software acceptance environment to test the modifications in. And finally database 3 will be used as the production live environment.

On the Business Notification server 2 services were created during installation. One or both of these 2 services connect to the Navision database that has been specified during installation. It uses the registry information found in key 'NAS Parameters' for this.

I already discovered that is very simple to let the Business Notification Server connect to another database by altering the database name in the 'NAS Parameter' key and restarting those services.

This is fine during the implementation period. But once the user goes live the Business Notification Server will connect to the Navision Live database. From that moment on we won't let it happen that the Business Notification Server will be disconnected from the Live Navision database and be connected to another one for obvious reasons.

Questions:
I would like to know if there is a possibility to create 2 more services for each additional Navision database we want Business Notification Server to connect to. I realize that this requires additional registry keys too. Can this be done?

Is there some way to make this possible without the need of having to install two more additional Windows 2003 servers similar to the one that runs the Business Notification Server?

If this can't be done it would require 2 more extra server platforms, OS and so on which makes it even more expensive than it already is.