Timeline for db_datareader, db_datawriter and db_owner permissions
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 16, 2015 at 10:29 | vote | accept | Ozkan | ||
| Dec 16, 2015 at 10:01 | history | edited | Julien Vavasseur | CC BY-SA 3.0 |
added 494 characters in body
|
| Dec 16, 2015 at 9:54 | comment | added | Julien Vavasseur | at the database level, db_owner is the highest you can go although you can still check any lower level roles such as db_datareader or over roles with rights already included in db_owner. | |
| Dec 16, 2015 at 9:53 | comment | added | Ozkan | These permissions are for a service account and db_owner is a prerequisite. But sometimes I see that for a SQL Login all three permissions are selected (db_datareader, db_datawriter and db_owner), actually when selecting db_owner, then db_datareader and db_datawriter should be grayed out because it's unnecessary to select those also | |
| Dec 16, 2015 at 9:48 | history | answered | Julien Vavasseur | CC BY-SA 3.0 |