The Service Bus for the Connected Business
I'm currently working in a development environment. I have been dropping and recreating the Neuron database (via Neuron Explorer) whenever I install a new version. No problems here.
I suspect, however, that this isn't necessarily what I should recommend when promoting the new version up through our environments (qa, staging, production).
Is there a best practice for deploying new versions of Neuron? How would I know if the Neuron database needs updated? How do I determine the database update process?
Tags: database, deploy, environment, promote, update
Views: 61
It probably not necessary to drop the database for every Neuron update since it's rare that the database schema changes from release to release.
However, to be certain if the database needs updating or not you can always create a new database with the latest version of Neuron and compare the new database schema to the old database schema. Visual Studio contains tools to compare database schemas but there are other products as well such as redgate. If the tool detects schema changes you can then run the sql script on the old database.
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin.
Powered by
