Contents
What causes service broker to fail in SQL Server?
ALTER DATABASE statement failed. This error happens when a Service Broker enabled database is restored or copied to the same SQL Server instance where the original database resides, as a result, both databases end up having the same Service Broker identifier.
Why does my SQL Server have the same service broker identifier?
This error happens when a Service Broker enabled database is restored or copied to the same SQL Server instance where the original database resides, as a result, both databases end up having the same Service Broker identifier.
How to configure service broker with availability groups?
Configure the route as follows: Set ADDRESS to the listener IP address of availability group that hosts the service database. Set PORT to the port that you specified in the Service Broker endpoint of each of the remote SQL Server instances. The following example creates a route named RouteToTargetService for the ISBNLookupRequestService service.
Where do I find my service broker identifier?
This unique identifier also helps the Service Broker application to correctly route and deliver the Service Broker messages to the correct instance of SQL Server. The “service_broker_guid” column of sys.databases catalog view returns this unique identifier value for each database on SQL Server.
Can you use service broker in Azure SQL?
Cross-instance service broker message exchange is supported only between Azure SQL Managed Instances: CREATE ROUTE: You can’t use CREATE ROUTE with ADDRESS other than LOCAL or DNS name of another SQL Managed Instance. Port specified must be 4022. See CREATE ROUTE.
What happens when service broker has 5 failed concurrent transactions?
Also don’t forget to look at your queues if they hold any errors in them. After five failed concurrent transactions you will get what is known as Message Poisoning after which your queue will get disabled and a Broker:Queue Disabled event will be fired.