Timeline for Setting up users and admins with schema privileges
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2012 at 19:55 | comment | added | Andreas Wolter | separation of duties and objects for those - that is a basic principle and by far not cumbersome if you think bigger than of 5 tables and procs | |
| May 7, 2012 at 19:48 | comment | added | Andreas Wolter | A clean design helps. Otherwise you end up with problems like these. - you could use synonyms ans Execution Context to get around your specific problem with the app. Otherwise you're out of luck and have to Grant each proc separately | |
| May 7, 2012 at 18:13 | comment | added | DForck42 | definatley can't do this. the application calls the stored procedures by schema.procname. by moving the procs to different schemas we completley break the app, and we're getting ready to do a final push to production. hence why i'm trying to clear up security. | |
| May 7, 2012 at 17:35 | comment | added | Thomas Stringer | That's pretty clunky and cumbersome, I don't know if I'd recommend that strategy. | |
| May 7, 2012 at 17:22 | history | answered | Andreas Wolter | CC BY-SA 3.0 |