Neuron ESB User Network

The Service Bus for the Connected Business

Neuron Database Upgrades

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: 11

▶ Reply to This

Replies to This Discussion

Permalink Reply by Brandon on April 20, 2011 at 9:42am

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.

 

RSS

Neuron ESB Product Support Forums and Communities

Latest Activity

Nick Novotny posted a discussion

Script to stop/restart service connectors

Is there a way to turn on and off service connectors through the neuron api?  Right now I need to go to Endpoint Health in Activity, and right click to stop and restart service connectors, I would like to have a script to do this.  Is this possible? Thanks,-Nick NSee More
May 11
2 Comments
Profile Iconsuresh datla and Mahboob joined Neuron ESB User Network
Apr 24
Nick Novotny posted a discussion

Msmq network transport error logging

We have multi-casting one way messaging through a remote msmq server using wcf services for our system. One day one of our many environments got a message to multicast…and didn’t send anything out.  We have a pipeline step to audit the incoming message, topic properties to move msmq messages to a dead letter queue after a specific amount of time, and a service policy to move messages to the failed neuron db table after a specific amount of time/retries (matching the msmq network properties to…See More
Apr 13
1 Comment
Stas Makutin posted a discussion

Load-balancing using Neuron

I want to implement following scenario using Neuron ESB:- get big list of working items from somewhere (let's say some database)- split this list to small "batches" of working items- send these batches each to particular instance of specific subscriber (Worker), so each that instance will process assigned batch in parallel with other instances- collect feedback (is processing complete/failed) + implement some fail-over mechanism (resend failed batches, monitor if batches weren't processed…See More
Apr 11
2 Comments
Profile IconStas Makutin, Bjorn Thomsen and Steve Harclerode joined Neuron ESB User Network
Apr 11
MH is now a member of Neuron ESB User Network
Mar 29
Welcome Them!
Profile IconCraig Muir and mehnaz joined Neuron ESB User Network
Mar 12
John Ryan posted a discussion

Trouble creating a net.msmq Client Connector

Has anyone successfully created a Client Connector using Net.msmq?I'm trying as many different configurations as i can to post a message to a Client Connector but i get the following error on my client app:"The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."It looks as though my client connector endpoint is not binding to the WAS correctly.If anyone has any ideas, i'd love to hear them.Here are my Client…See More
Mar 6
1 Comment

Badge

Loading…

Get Badge

© 2012   Created by Neuron Admin.   Powered by

Badges  |  Report an Issue  |  Terms of Service

Sign in to chat!