Enable SQL Service Broker in SQL Azure
Service Broker should be available in Windows Azure.
This request is now covered under the new Managed Instance offering → https://azure.microsoft.com/en-us/blog/migrate-your-databases-to-a-fully-managed-service-with-azure-sql-database-managed-instance/
Niraj Oza commented
Please enable this feature
Need to be able to use Service Broker on elastic pool. Please add.
Please enable Service Broker on Azure SQL single databases. badly needed. x 2
Please enable Service Broker on Azure SQL single databases. badly needed.
Please enable Service Broker on Azure SQL single databases. The Managed Instance is way too expensive.
"This request is now covered under the new Managed Instance offering"
No, it isn't!
Managed Instance costs around £1250 per month for a low-end spec.
An Elastic Pool costs around £105 per month for a low-end spec.
A single database costs around £12 per month for a low-end spec.
Not one single one of my clients wants to suddenly go from paying £12 per month (or a share of £105 per month) up to £1250 per month just to get Service Broker.
This is a key part of SQL functionality, and used extensively in our software.
Without it, we can't offer Azure-hosted databases for our software.
Rafael Bolaños commented
Please enable Service Broker for SignalR. Thanks!!
Please enable Cross instance service broker in Managed Instance.
Please add service broker on azure sql
tayseer tahtawy commented
please get service broker and triggers available in windows azure
Boris Ryvkin commented
Could you make Service Broker available in Azure SQL (single database)? This is critical for us.
All thanks Microsoft 😎
I’ve been waiting this for years, and it finally worked with me!
[Deleted User] commented
Covered under new Managed Instances does not solve the issue for many. What about classic Azure SQL (single databases)?
do anyone have any alternative for SIGNAL R to work
Provide Alternatives please
Jamie Thomson commented
Service Broker became available in (what used to be called) SQL Azure yesterday (2018-03-07) with the announcement of the GA of Azure SQL Database Managed instance:
We’re excited to announce the preview of Azure SQL Database Managed Instance, a new deployment option in SQL Database that streamlines the migration of SQL Server workloads to a fully managed database service. This new Managed Instance deployment option provides full SQL Server engine compatibility and native virtual network (VNET) support.
With Managed Instance, you can continue to rely on the same SQL Server tools you’ve used and loved for years—in the cloud, too. These include features such as native database restore, SQL Agent, Database Mail, Service Broker, Common Language Runtime (CLR), and Change Data Capture.
So I guess this uservoice ticket can be closed, right?
Please do add "Service Broker"
Michal Poreba commented
As others before me I have a case where a potential move to Azure was abandoned at POC stage because of missing Service Broker which can be an effective tool to distribute load, implement data centric messaging solution right in the database and very importantly allow for asynchronous processing in SQL Server (asynchronous triggers). Another scenario is near real-life data consolidation from multiple source databases. Are there any plans of enabling it in Azure one day, or is it completely of no interest or value to Microsoft?
If you don't want to support the Broker then provide a valid alternative that the .Net SqlDependency can use instead.
Matthew Whited commented
Bummer this is still missing... it's only been 8 years