August 17, 2018 at 8:54 pm
I have a DB which I switched to read only. User couldn't run reports (I don't know why) but when I set the setting to false for read only, user complained about permission issues as he was unable to create any tables. Does changing DB setting change permission? I don't think so but I would like to educate myself. Any advise or info?
August 18, 2018 at 2:26 am
NewBornDBA2017 - Friday, August 17, 2018 8:54 PMI have a DB which I switched to read only. User couldn't run reports (I don't know why) but when I set the setting to false for read only, user complained about permission issues as he was unable to create any tables. Does changing DB setting change permission? I don't think so but I would like to educate myself. Any advise or info?
Read-only means that nothing can be changed in the database. That's not just the "data" in your table's, that's also creating objects, deleting them, altering, and INSERT and UPDATE statements (and others).
Setting a database to read-only doesn't remove every users "write" permissions, it simply "blocks" the actions. If the database comes out of read-only then the users would have permission to do whatever they did before.
If they are saying your user is saying they can create objects and they shouldn't be able to, clearly they have more permissions than they should. What permissions does the user have? What should they have? Only you will know the answers to those questions.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply