Click here to Skip to main content
15,867,308 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
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.
Posted
Updated 21-Mar-18 11:02am

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[^]
 
Share this answer
 
v2
Comments
Herman<T>.Instance 23-Mar-18 10:00am    
No thank you
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

GRANT Service Broker Permissions (Transact-SQL) | Microsoft Docs[^]
 
Share this answer
 
Comments
Herman<T>.Instance 23-Mar-18 10:01am    
We tried that. But when running the statement SqlDependency.Start(configstring) you get 3 exceptions. The above rights where granted. Only adding role db_owner fixed this issue.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900