October 19, 2016 at 12:15 am
Comments posted to this topic are about the item The Backup Operator
October 19, 2016 at 1:44 am
Simply, when the backup agent job makes the backups it makes them from the master database context (for example) and not changing the contexts for each of the databases.
So no need to confuse with the db context.
Igor Micev,My blog: www.igormicev.com
October 19, 2016 at 5:30 am
Right, unless you miss the context used in the first set of permissions granted. :alien: Need more coffee.
October 21, 2016 at 7:47 pm
Interesting. Good question.
I thought that might be how it is, but was unsure because the permission is assigned to a database user, not to a login, so read up on cross database ownership chaining - and the only conclusions I reached were (i) that documentation is pretty dreadful and (ii) that it looked as if chaining might be required, but also might not, depending on what the documention means and/or what it's left out.
So I convinced myself that my first idea must have been wrong, and thus got it wrong.
Tom
October 22, 2016 at 4:59 pm
BWAA-HAAA!! The correct answer isn't actually available on this question. 😉 There is no way that I'd grant a non-DBA the privs to do a direct backup even on a Dev box. :w00t:
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2016 at 2:54 am
Thanks for the question.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply