Can't agree fully with disabling analysts from creating certain entities like tables and views. It is generally correct for prod databases but I think it's better to give them some freedom of action in their own DB copies, including letting them see their colleagues' DBs to test hypotheses freely
In that case, it sounds more similar to the Developer role (with the Dev creation permissions). But of course all of this is customizable to you and your team.
Looking for help with your team's data strategy? → www.kahandatasolutions.com
Looking to improve your data engineering skillset?→ bit.ly/more-kds
Insightful. Glad to see you back.
Thank you man! Always good content!
Appreciate it!
Good stuff!!!
Thanks!
Great content!!
Can you please provide the use role script if possible?
Can't agree fully with disabling analysts from creating certain entities like tables and views. It is generally correct for prod databases but I think it's better to give them some freedom of action in their own DB copies, including letting them see their colleagues' DBs to test hypotheses freely
In that case, it sounds more similar to the Developer role (with the Dev creation permissions). But of course all of this is customizable to you and your team.