November 4, 2020 at 8:41 pm
Thank you. There are only three databases that have service broker set to 0. And its the same value on the primary and the secondary replicas.
November 4, 2020 at 10:20 pm
You stated you are now getting an error related to a service broker - which means one or more are enabled. And yes, if you have a service broker in an AG database it needs to be setup and configured on *all* replicas.
The most likely reason for the error is that the secondary was not setup and enabled - so now that you are running on that secondary the service broker isn't running and you are getting that error.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
November 5, 2020 at 3:21 pm
Thank you. All the databases show the same value/flag for service broker on both the replicas. Example, databaseA shows 0 on both replicas, and databaseB shows 1 on both replicas.
November 5, 2020 at 4:41 pm
Re-thinking on what you mentioned. So, we have databases that have the service broker disabled on both replicas and also some databases that have it enabled on both replicas.
But I see that there is no service broker endpoint configured on any replicas. So, either the service broker endpoint needs to be created on both replicas or have all databases set to disabled on both replicas. Is that how it should be? What would be the repercussion if things are left as is (except for the annoying messages every 15 minutes)?
Thank you much!
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply