Servicebroker默认使用其他架构 [英] Servicebroker default on other schema

问题描述

有没有人成功让SQL Server中的ServiceBroker不能在架构DBO（默认）上运行，而是在较低级别上运行，如db_datareader？



我尝试了什么：



我无法完成它。我必须将创建的用户设置为具有db_owner架构权限。为了我的目的，这是一个矫枉过正。

Hi,

has anyone ever succeeded to have the ServiceBroker in SQL Server not run on schema DBO (default) but on lower levels like db_datareader?

What I have tried:

I can't get it done. I have to set up the created user to have db_owner schema rights. For my purpose that is an overkill.

推荐答案

好吧，你似乎没有任何反应，所以也许是时候开始考虑 PostgreSQL 。

这是一篇关于PostgreSQL中的通知的文章： PostgreSQL通知示例 [ ^ ]



BTW替代方案可能是SQL Server更改跟踪：关于更改跟踪（SQL Server）| Microsoft Docs [ ^ ]

Well, you seem to get no reactions, so maybe it's time to start thinking about PostgreSQL.
Here's an article about notifications in PostgreSQL: A PostgreSQL Notification Example[^]

BTW an alternative might be SQL Server change tracking: About Change Tracking (SQL Server) | Microsoft Docs[^]

不能说我试过了，但是在这两者之间：

kreel位：Microsoft SQL Service Broker的有用数据库角色：db_servicebroker [ ^ ]

服务代理的最小帐户权限 [ ^ ]

只要你有以下情况就可以工作：

• 接收队列
• 发送FROM服务
• 合同参考

Can't say I've tried it, but between these two:
kreel bits: Microsoft SQL Useful Database Role for Service Broker: db_servicebroker[^]
minimum account permissions for service broker[^]
it's supposed to work so long as you have:

• RECEIVE on queues
• SEND on FROM service
• REFERENCES on contract

这篇关于Servicebroker默认使用其他架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！