{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 时光不老，我们不散 的问题《Is there a scalable alternative to SQL Server Quer》','https://www.manongdao.com/q-800856.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
SQL Server Query Notifications is a great tool, but it doesn't seem built to scale very well. Every application that wants/needs notifications has to keep an open connection to the database for the duration of the time it wants notifications (typically the entire time the application is running).
I am open to creative solutions. Off the top of my head I just thought of putting a service on the server that would subscribe to SQL Server Query Notifications which could then notify the client applications. In this case you have only 1 database connection open (and why not just leave it open all the time), and then your client applications could just subscribe to the service for notification.
Ideas??
You may want to look into building your own solution using SQL Server Service Broker and db_mail or external activators.