Timeline for Assign db_owner to all users at once
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2020 at 15:18 | history | edited | Aaron Bertrand | CC BY-SA 4.0 |
added 4 characters in body
|
| Jul 19, 2016 at 16:48 | comment | added | Kenneth Fisher | Sometimes you have no choice, I understand completely. If you can (and aren't already) you might put the application on it's own isolated instance. I still stand by getting something in writing saying you are against this and not responsible for any damage/data loss/data theft caused by doing it. | |
| Jul 19, 2016 at 16:33 | comment | added | QWE | I am well aware that it is not a good idea to give db_owner to everyone, but...we are installing a very specific application. Every users who wants to use this application will need db_owner. We already tried walkarounds but the aplicaton is rather primitive in nature. | |
| Jul 18, 2016 at 21:53 | comment | added | Kenneth Fisher | @JoePlatano I tried to add db_owner to public but you can't change the membership of public. CONTROL database is almost identical to db_owner. Literally the only diff is the ability to add other people to db_owner. You can even grant others CONTROL. | |
| Jul 18, 2016 at 21:23 | comment | added | Joe Platano | nice approach. is there also the possibility to add the db_owner role? i dont know why the OP asked to assign everyone to the role and i think as you it is not a good idea. | |
| Jul 18, 2016 at 18:15 | history | answered | Kenneth Fisher | CC BY-SA 3.0 |