Dan Munns Posted January 30, 2019 Posted January 30, 2019 Hi all, Is there a role which allows access to database direct but isnt a system admin / super user role? I thought that advance reporting admin would do it but apparently not. If no role is available does anyone know the settings to allow for read only access to database direct so I can create one. Thanks Dan
mojahidm Posted January 30, 2019 Posted January 30, 2019 +1 If the role should only be used for an emergency or when first setting up the system, what do we use as a day to day for access to database direct? Thank you, Mojahid
Victor Posted February 1, 2019 Posted February 1, 2019 @Dan Munns (long time no speak) @mojahidm Only a "Super User" will be able to use database direct. This is unlikely to change due to the potential issues this might cause (having direct access to DB). The question is, why do you need to give such access to a user?
Dan Munns Posted February 1, 2019 Author Posted February 1, 2019 I just want to create a read only user so that they can read the various tables and column names to create some reports. But having them have super user access is obviously a bad idea. Otherwise I am going to have to create a data dictionary in excel for them. Which will involve lots of work I don't fancy signing up to..... 3 hours ago, Victor said: @Dan Munns (long time no speak Did you miss me?
Victor Posted February 4, 2019 Posted February 4, 2019 On 2/1/2019 at 7:18 PM, Dan Munns said: so that they can read the various tables and column names to create some reports @Dan Munns why not give them access to app entity viewer for this? On 2/1/2019 at 7:18 PM, Dan Munns said: Did you miss me? Sometimes it can get lonely on the dark side...
Dan Munns Posted February 4, 2019 Author Posted February 4, 2019 @Victor I knew this would be your answer. I felt it in the force.... The entity viewer isn't the most user friendly thing in the world and to find out database column names rather than display names for quite a few tables means switching over to the database schema viewer, which always reverts to the top of the list rather than keeping the table you were looking at and is just more of a pain (especially as the names don't always match up.) Far easier to have read only access to the database, see what columns you need then pop over to entity viewer if you need a table join that you cant work out. The only really good schema viewer I have used was about 5 years ago with some software I cant even remember but you could select 2 - 3 tables and it would list all the columns for each table and colour code the fields where you could create the table joins.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now