Create DBADashService user on AWS RDS and GCP CloudSQL #894
Replies: 2 comments 1 reply
-
Hi, we don't have any footprint in GCP so I'm not easily able to test issues on this cloud platform. The RDS issue with syssessions permission has been fixed #891 in 3.5.1 - just released yesterday. If you upgrade to the latest version it should be working. |
Beta Was this translation helpful? Give feedback.
-
Thank you David. For GCP Instances, we are getting these 2 errors all the time, can you please help me to understand for which data collector it is giving these errors -
|
Beta Was this translation helpful? Give feedback.
-
Hi @DavidWiseman , Hope you are doing good.
I was trying to add few AWS RDS and GCP CloudSQL instances to DBA Dash monitoring, however, while creating the DBADashService user, we can not make it sysadmin, so I tried using minimal permissions, but it is still failing due to limitations on these cloud db services.
https://dbadash.com/docs/help/security/#running-with-minimal-permissions
Error -
Msg 4613, Level 16, State 1, Line 4 Grantor does not have GRANT permission. Msg 15151, Level 16, State 1, Line 14 Cannot alter the role 'db_datareader', because it does not exist or you do not have permission. Msg 15151, Level 16, State 1, Line 15 Cannot alter the role 'SQLAgentReaderRole', because it does not exist or you do not have permission.
I tried to use the existing admin server login with setupadmin permission, but DBA Dash collectors are failing with multiple errors -
The SELECT permission was denied on the object 'syssessions', database 'msdb', schema 'dbo'. Microsoft.Data.SqlClient.SqlException (0x80131904): User does not have permission to perform this action.
Beta Was this translation helpful? Give feedback.
All reactions