We have achieved persistent mechanism with activemq as it has built in support to store messages in SQL database.
But our requirement to store message in SQL using rabbitmq but after some research we are unable to find any strong support or help for this.
Any suggestion would be great help to us.
RabbitMQ uses Mnesia DB to store the definitions about queues/exchanges etc. and it uses a custom DB to store the messages.
Right now, with RabbitMQ is not possible to use an external database to store the messages as ActiveMQ
maybe in the future.
Related
So I was moving my NSB setup off of SQL server and onto azure service bus and figured I might as well use azure storage for persistence as well. I'm unclear on how to set this up because I'm also using outbox and I can't use azure storage with it. I'm using the web.config for connections strings, and it sort of only lets me set NServiceBus/Persistence once, so ... I'm a bit lost
Unfortunately, due to various reasons the outbox is only supported on SQL-Server and RavenDb. Read more about it here : https://docs.particular.net/nservicebus/outbox/
At the bottom of the document there's a note that only those two persisters support the outbox feature.
Add to what Dennis said - you cannot use Storage Persistence with the Outbox feature. Outbox feature requires business data and outgoing transaction to participate in the same transaction. This is only possible with Azure SQL server. With Azure Storage persistence this is not an option. Storage supports table batched operations, but not transactions.
I am looking for specific help setting up message types/contracts/queues and EA to post notifications of SQL table update/inserts to an existing RabbitMQ system. The destination quese already exist. SQL-to-SQL documentation exists, but not going SQL-to-RabbitMQ.
If I understand your question, you want to have a sql table insert/update to send a rabbitmq message?
If you wanted to do this, there are several ways I could imagine this being setup, though I think this maybe bad practice.
You could create a sql clr to allow sql server to send a rabbit msg and then incorporate that into the insert/update, either by adding it to the stored procs if ones are used, or maybe setting up a job that uses change tracking.
We are using Sql 2012 database server. When ever the db modifies we want it to trigger a message that can be stored in a queue using activemq.
We are not sure how can we code to trigger a db so that it sends a message.
Can we directly make the message generated from db to get queued in activemq without any java interface in between. I would want to know whether we can achieve this or not.
3.Are there any other ways to set up a communication between sql server and activemq say between database services and activemq services(does activemq have that)
PS i am a new user of activemq. Any leads to solve these queries is appreciated.
Please don't as SQL Server to do this. SQL Server is designed to store data. You are asking too much of it. Depending on how many places you would want to add to this queue from, I would choose one of the following solutions:
If you want to add to this queue from a bunch of different places, and don't want to change existing code, create an application to move items from SQL Server to ActiveMQ. The items in SQL Server can be populated by a trigger.
If there are only a few places that add to this queue, add that logic to the application so that every write to SQL Server will also write to ActiveMQ.
If you really still don't want to modify any code, you can configure ActiveMQ to use SQL Server as its persistence database. Then you can modify its data and hope that it plays nice. This is definitely not preferable. I would rather put CLR code into SQL Server to push data to ActiveMQ.
I want to use rabbitMQ to store new transactions(records) that are happening in the local database into the remote similar database.
Any suggestions, ideas on this?
Can you share the reason of wanting to use RabbitMQ as the store and forward mechanism to the remote database. I believe most databases already have mechanisms to replicate/backup to a remote database installation. These are tuned to the database and tend to work very reliably. RabbitMQ will not help you shard database operations across multiple remove database instances either.
Why RabbitMQ?
I work with Service Broker. I need to know which Service Broker entities (message types, contracts, etc.) have been added to the database I am dealing with.
The question refers to MS SQL Server 2005.
Thank you!
Nice article on the subject of service broker management views here...
Troubleshooting Service Broker Problems